Book a 30-min callSee what we do →

01 — Signs

Sound familiar?

  • The store slows down right at the peaks

    Black Friday, CyberMonday or a campaign: when more people come in, the site lags or checkout fails. Every one of those minutes is a lost sale.

  • Stock and prices that don't match

    The store sells something that isn't there, or shows a price different from the ERP's. Someone fixes it by hand, and late.

  • Orders keyed in twice

    Orders go from the store to the ERP or to logistics by hand or through a spreadsheet. Errors show up when the customer complains.

  • Payments that are hard to reconcile

    What comes in through Mercado Pago, Payway or other methods doesn't obviously match the orders, and reconciling takes days.

  • Every team has its own number

    Store, ERP and marketing data live apart. Measuring a campaign means a spreadsheet put together by hand.

  • A platform nobody dares to touch

    Every update is scary, extensions pile up and the site keeps getting slower.

A large store is not just a catalogue with a checkout. It's a system that has to talk to the ERP, payments, logistics and data, and hold up on its biggest sales day.

02 — What we do

From the platform to the last connected system.

  • Platform

    We build on Adobe Commerce (Magento) and WooCommerce, or make a custom store, depending on volume, catalogue and your team. If you already have one, we work on it.

    Adobe Commerce · WooCommerce · Custom

  • ERP integration

    Stock, prices, customers and orders in sync with SAP or another ERP, with a log of every step and alerts when something fails.

    SAP · APIs

  • Payments

    Mercado Pago, Payway and other payment methods, with instalments, a notification for each payment and the data to reconcile it with the order.

    Mercado Pago · Payway

  • Data and reporting

    Sales, catalogue and behaviour in BigQuery, so every team measures channels and campaigns with the same number.

    BigQuery · GA4

  • Performance and peaks

    Caching, a CDN and infrastructure that scales on its own on the busiest days, with Core Web Vitals in the green.

    CDN · Autoscaling

  • Logistics

    Orders that flow to the warehouse and the carrier on their own, with the shipping status visible to the customer.

    Shipping · Tracking

03 — How we work

In stages, without stopping sales.

  1. 011–2 weeks

    Assessment

    We review the store, its integrations and its traffic. The result is a prioritised plan (what to fix, integrate or migrate) and the budget for the first stage.

  2. 024–8 weeks

    First stage

    Whatever costs the most sales today: usually the ERP integration or performance at the peaks.

  3. 03Per the plan

    Next stages

    Integrations, improvements or a platform migration, each with its own scope and budget, which you approve before we start.

  4. 04Black Friday · CyberMonday

    Before every peak

    Before every big event we set up autoscaling (on Adobe Commerce Cloud or your cloud), so the store adds capacity on its own when traffic comes in.

What goes in writing

  • Scope, timeline and budget for each stage, approved before we start.
  • Every change reaches production tested and with a way to roll back.
  • The code, the data and the accounts belong to your company from day one.
  • Documentation so your team or your agency can carry on without depending on us.

04 — Team experience

We've done it at scale.

Leading consumer electronics retailer · Argentina

A high-volume Adobe Commerce platform, built from scratch

Before founding Pipa Code, one of us led, at a software factory, the planning and delivery of the online store of a leading consumer electronics retailer in Argentina. He coordinated a team of 6 developers, worked directly with the business owners and oversaw the SAP and Google BigQuery integrations.

During that time he also worked with other high-volume, high-traffic stores across industries, with payment integrations such as Mercado Pago and Payway.

What it achieved

  • Launched on the planned date.
  • 100% of the agreed scope.
  • Stock, prices and orders integrated with SAP.
  • Sales data in BigQuery, available to the business.

This is the team's prior experience.

05 — FAQ

Frequently asked questions

Do you work with Adobe Commerce (Magento)?

Yes, we build on Adobe Commerce (Magento). The team has experience with high-volume stores integrated with SAP, BigQuery, Mercado Pago and Payway. We also work with WooCommerce and custom stores.

Do we have to switch platforms?

Not necessarily. It often pays to integrate and optimise the one you have. If a migration makes sense, we raise it in the assessment with its costs and risks, and it's done in stages, without stopping sales.

Can you get the store ready for Black Friday or CyberMonday?

Yes. We measure how it responds today, tune caching and the CDN, and set up autoscaling (on Adobe Commerce Cloud or your cloud) before the event. It's best to start early, not the week before.

Does it integrate with our ERP?

Almost always. The team has already integrated stores with SAP, and with other ERPs we work through APIs, files or the database, depending on what each one allows.

Do you work with our agency or our team?

Yes. We can take on the technical side (integrations, performance and infrastructure) and leave design and marketing to whoever already does them.

How much does it cost?

It depends on the scope. After the assessment we send you a staged proposal, with effort ranges and an explanation of what's left out.

Who owns the code?

Your company, from day one: code, data, access and documentation.

What's going on with your store?

Book a 30-minute video call or tell us what you want to solve and we'll get back to you within 24 hours.

How would you like to reach us?
1. Pick a day
2. Pick a time · Argentina time (GMT−3)
3. Your details

Select a day and time