ERP for e-commerce: what to check before choosing and how to switch without losing data
An e-commerce ERP brings together orders from the website, the marketplaces and the counter, deducts from a single inventory, issues the invoice and checks the payout. Before choosing, test it with a real week of orders and confirm that your data leaves with you. To switch, export everything before signing, keep the invoice XMLs and run both systems in parallel.
What does an e-commerce ERP need to do in 2026?
It needs to be the place where each channel's order, inventory, invoice and money meet. If one of those parts is left out, the store goes back to the spreadsheet.
| Function | What to check in the demo |
|---|---|
| Orders from every channel | Website, marketplaces and counter arrive in the same queue, in the same format |
| Single inventory | One SKU per variation, one balance, deducted instantly on every channel |
| Hold until payment | An order without Pix holds the product for a set time and releases it automatically |
| Invoicing | NF-e and NFC-e issued from the order, without retyping |
| POS | The counter sale deducts from the same inventory and goes into the same cash register |
| Shipping | The label comes out of the order, and tracking goes back to it |
| Finance | Pix, card and marketplace payout checked order by order |
| Data | Public API and full export, without depending on support |
The last row is the one that shows up least in the demo and weighs most in a switch. With a public API, another system reads and writes to the ERP. With a full export, the store takes its data along if it ever leaves.
How much does an ERP for an online store cost?
The price depends on volume, and each vendor measures volume differently. These are the plans of two ERPs common in online stores, on the pricing pages accessed on October 26, 2026:
| ERP | Entry plan | Highest published plan | What limits the plan |
|---|---|---|---|
| Bling | Cobalto, R$ 60 a month: up to 200 marketplace orders and 5 users | Elite, from R$ 1,250 a month | Marketplace orders and API |
| Olist ERP | Avance, R$ 66 a month: 2,000 listings | Domine, R$ 948 a month: 20,000 listings | Number of listings |
Both sites showed year-end promotional prices on that date. The table uses the list price.
Two details from the pages change the comparison:
- At Bling, POS, online store and manual orders don't count toward the limit, according to the plans page. A store that sells a lot at the counter pays for its marketplace volume.
- At Olist ERP, orders and users are unlimited on every plan. The limit is the number of listings.
Bling also includes an AI assistant on every plan, according to the same page. Query AI has become a standard feature in retail ERPs. What sets them apart is AI that acts in the operation, with a person's confirmation.
The monthly fee is not the whole cost. Add the online store platform, the marketplace hub and the WhatsApp used for customer service. And the hours the team spends copying data from one system to another.
A complete system or a system on top of your current ERP?
It depends on how much your current ERP already handles. If invoicing and inventory work and the problem is between channels, replacing everything is expensive and risky. If the ERP can't handle the volume or has no API, the switch pays for itself.
| The store's situation | Safest path |
|---|---|
| No system, everything on spreadsheets and a card machine | A complete system, with inventory, POS, invoicing and finance |
| The ERP works, but orders and payouts are scattered | Keep the ERP and add an operations layer on top, connected through the API |
| ERP with no API, or one that stalls at current volume | Switch, with a planned migration |
| Many marketplaces and thousands of listings | ERP with a hub, or a dedicated hub connected to the ERP |
Before deciding, ask the vendor:
- Is the API public and documented? Ask for the documentation link.
- How do I export everything, and in what format? Products, balances, customers, orders and finance.
- What counts toward the plan limit? Orders, listings, users or invoices.
- Who handles tax? Digital certificate, tax rules per product and the new tax reform fields (Complementary Law 214/2025).
- How much does onboarding cost and who migrates the data?
How do I switch ERPs without losing data?
Export everything before signing, import into the new one, check and run in parallel. The order matters, because the old system may go offline the day the contract ends.
What to export from the old ERP
- Products: SKU, GTIN, variations, price, cost, weight, dimensions, NCM and origin.
- Inventory: balance per warehouse on the cutover date.
- Customers: records with CPF or CNPJ and address.
- Open orders: those paid but not yet shipped.
- Finance: open accounts receivable and payable.
- Invoices: the XMLs of every invoice issued and received.
The XMLs need care. The tenth clause of Ajuste SINIEF 07/2005 requires the issuer to keep the NF-e in digital form for the period set by tax law. Art. 173 of the National Tax Code gives the tax authority 5 years, counted from the first day of the following year, to assess the tax. Keep the XMLs outside the old ERP and confirm the period with your accountant.
The switch in five stages
| Stage | What to do | Proof that it worked |
|---|---|---|
| 1. Export | Download the files from the list above | Totals match the old system's reports |
| 2. Test import | Upload the data to the new ERP | A sample of 30 products checks out, with variations and tax data |
| 3. Connecting channels | Connect website, marketplaces and labels to the new one | A test order from each channel arrives in the queue |
| 4. Parallel run | Run both for a slow week | Inventory and orders match in both, every day |
| 5. Cutover | Count inventory, adjust the balance and shut down the old one | The first invoice comes out of the new one, with the right series and number |
In stage 5, write down the series and the last invoice number used in the old system. NF-e numbering runs in sequence, and the first invoice from the new ERP has to continue from it. Agree on it with your accountant before the cutover.
Pick the cutover week far from peak sales dates. Switching ERPs during Black Friday week is changing a tire while the car is moving.
How CERNE solves it
CERNE can be the store's ERP or work on top of the system it already uses.
- No system yet? CERNE becomes the store's ERP: orders from every channel, single inventory, POS, invoicing through Focus NFe, finance and marketplaces.
- Already use Bling, Tray or Nuvemshop? CERNE integrates and organizes orders, inventory and cash on top. Marketplaces come in through Bling.
- Payout checked. Pix, card and marketplace payout go into finance linked to each order. Whatever doesn't match shows up before the close.
- Onboarding in stages. In the first month, orders and inventory. Then POS and invoicing, finance and shipping, and finally marketplaces and business orders.
- Migration with our team. The assessment lists what comes out of the current system and in what order.
The retail and e-commerce package was built in The Middle's operation. With the operation structured, The Middle moved to B2B and expanded into other lines of business. See the retail and e-commerce page and the module rollout. For margin per channel, see Mercado Livre and Shopee fees; for balance across channels, physical and online store inventory.
Start with an assessment
Switching ERPs without an assessment means finding out during cutover week what doesn't migrate. Start with an assessment of your operation: our team maps your channels, your current ERP and the migration path. Schedule the assessment.
Frequently asked questions
- What does an e-commerce ERP need to have?
- Orders from every channel in one queue, a single inventory per SKU, NF-e and NFC-e issuing, a POS for the counter, finance with reconciliation of the marketplace payout and integration with the shipping label. And a public API, so the store isn't locked into it.
- How much does an ERP for an online store cost in 2026?
- On the pricing pages accessed on October 26, 2026, Bling ranges from R$ 60 (up to 200 marketplace orders) to R$ 1,250 or more a month, and Olist ERP from R$ 66 to R$ 948, with a limit on listings. Both showed promotional prices on that date.
- How do I switch ERPs without losing data?
- Export before signing: products with SKU, variations and tax data, balance per warehouse, customers, open orders, accounts receivable and the invoice XMLs. Import into the new one, check a sample and run both in parallel for a few days before the cutover.
- How long does the store need to keep the invoice XML?
- Ajuste SINIEF 07/2005, tenth clause, requires the issuer to keep the NF-e in digital form for the period set by tax law. Under art. 173 of the National Tax Code, the tax authority has 5 years, counted from the following year, to assess the tax. Confirm the period with your accountant.
- Do I need an ERP and a marketplace hub?
- Not always. Several retail ERPs already receive orders from the marketplaces. A hub makes sense when the store has many listings, many accounts or channels the ERP doesn't cover.
Sources
- Bling, Planos, accessed October 26, 2026
- Olist ERP, Planos, accessed October 26, 2026
- CONFAZ, Ajuste SINIEF 07/2005, tenth clause
- National Tax Code, Law 5.172/1966, art. 173
- Complementary Law 214/2025 (IBS and CBS)