Search "ERP for ecommerce" and you get NetSuite, a connector app, and a promise that one system will own Shopify, Amazon, WooCommerce, stock, and the books. Fine products. Often the wrong first project if you import finished goods and sell them on those channels.
You are not standing up a multi-entity finance stack. You are trying to get four answers before the next container is booked:
- What can Shopify actually sell, and what can Amazon actually fulfill?
- What did we order, and what did the factory confirm?
- When will the units be sellable, not just "ex-factory"?
- What did each SKU cost after freight, duty, and inbound: the number finance will accept?
I wrote this for that week. What an ecommerce ERP has to do when Shopify, Amazon FBA, and maybe Woo share a catalog, when the admin plus a sheet is finished, and when you should not buy a suite because a dashboard said "low stock."
If Shopify is the only channel that matters, use the Shopify ERP walkthrough. If Amazon FBA is the larger book, use ERP for Amazon FBA. If you are still choosing a category, not an ERP, use the supply chain management software map. Stay here when the same inbound has to land in more than one storefront.
If You Sell On Shopify, Amazon, And Maybe Woo
You import finished goods. The POs repeat. Shopify, Amazon FBA, or WooCommerce already take the customer order. Stock, cost, and the open factory order already live in three places.
Skip the enterprise ERP shortlist if you do not have a controller, multiple entities, or a finance team that will own the implementation. Those suites solve a real problem. A founder with four factories, an 80-SKU catalog, and two channels will spend the year configuring a process they do not have.
Need the factory scorecard before you migrate anything? Start with the supplier evaluation matrix and the templates. If the fire is the customer-order queue, not the inbound, use Shopify order management software.
What Ecommerce ERP Means When You Have Three Channels
ERP is the general ledger plus the modules that touch it: inventory, purchasing, sometimes CRM. Enterprise resource planning is the textbook name. Shopify, Amazon, and Woo are sales and fulfillment channels inside that room. They are not the whole business.
For an importer the useful meaning is narrower. Software has to follow one purchase from the factory to sellable stock, and keep the cost of that path on the SKU. The objects are the PO, the documents, the dates, the inbound charges, and the Shopify, FBA, and Woo positions those units will land in.
A lot of "ecommerce ERP" demos are a storefront connector wearing an ERP name. The NetSuite app for Shopify is a real product. Amazon connectors exist in the same shape. The hard work is still field ownership, not the install button. Product-level landed cost for a mixed container is not why most ERPs exist unless you build it. A connector may move an order and still send the wrong warehouse or price. The same test applies to any Shopify supply chain app you shortlist.
$11.20 In Shopify, $14.85 In The Documents
A brand sells the same mug on Shopify, Amazon FBA, and a Woo store. Factory quote is $9.40. Shopify still has last year's unit cost at $11.20. Amazon ads were planned on that number. Woo's cost field was never updated.
Channel positions on a Tuesday in July:
| Location | What The Screen Says | What Is Actually True |
|---|---|---|
| Shopify available | 420 | 90 of those are reserved on open orders |
| Amazon sellable | 180 | 240 more are inbound, not sellable |
| Woo on-hand | 95 | 20 are damaged from the last receipt |
| The PO sheet | 800 "on order" | Factory confirmed 740, ship date slipped 9 days |
The last three POs, measured to the day the unit was actually sellable:
| PO | Days To Sellable | Unit Cost After Documents |
|---|---|---|
| March inbound | 59 | $13.10 |
| May inbound | 63 | $13.75 |
| July inbound | 74 | $14.85 |
July's documents, 2,400 units ordered, 2,340 sellable after inspection:
| Line | Amount |
|---|---|
| Factory invoice (2,400 × $9.40) | $22,560 |
| Ocean freight, revised after booking | $5,820 (sheet had $4,100) |
| Duty and brokerage | $2,160 |
| Trucking, prep, FBA inbound | $4,190 |
| Sellable units | 2,340 |
($22,560 + $5,820 + $2,160 + $4,190) / 2,340 = $14.85.
They treat Shopify 420 as the cover number and reorder when it "looks low." Amazon already has a transfer in flight. Woo is selling through damaged units. Actual lead time from the last three shipments is about 65 days. At 55 units a day across the three channels they needed roughly 3,600 units of cover plus safety, not 420. The Shopify listing goes down while the inbound is still on the water. Amazon stays up on the inbound that has not received. Woo oversells the damaged 20.
Price and ads were planned on $11.20. July put the unit at $14.85. Every unit is $3.65 light before referral fees, FBA storage, or returns.
The Shopify number was on the product page. The Amazon number was in Seller Central. The dates were in WeChat. The $14.85 was in a PDF. Run the legs through the lead time calculator and the cost through the landed cost calculator. If you cannot reconstruct the $14.85 and the 74-day inbound from one record, you do not have an ecommerce ERP. You have three storefronts and a folder.
What The Software Has To Cover
Ignore the homepage that leads with "AI-powered warehouse orchestration." Score the product against the work between "Shopify says we are low" and "this SKU is sellable at a cost finance will accept on every channel."
Channel Stock Is A Hint, Not The PO
Shopify, Amazon FBA, and WooCommerce do not share a warehouse. Units may sit with the factory, move by sea, wait at a port, sit in an FC, sit at a 3PL, or sit on a store shelf. Reserved, inbound, damaged, and available-to-sell are different numbers.
Software does not have to replace your inventory app. It does have to stop you from placing a PO against a number that is already reserved or sitting in the other channel. Size buffers with a safety stock calculation, not a round number.
If locations, not supplier execution, are the constraint, read the ecommerce inventory guide.
The Purchase Order Is The Record
A useful purchase order keeps supplier, SKUs, quantities, agreed cost, Incoterm, promised date, and status, including partials and the revised ship date. If a date change only exists in chat, the PO is decoration.
Procurement software for small business is the buying-process version. The ERP test is narrower. Can a second person open the PO and see what the factory confirmed, and which channel the units are headed to?
Documents Sit On The Order
Commercial invoices, packing lists, bills of lading, freight invoices: same record as the PO. Invoice processing is the capture version. Extraction helps. A human still has to confirm quantity, currency, and which PO the bill belongs to.
Landed Cost By SKU And Shipment
Factory price, inbound charges, allocation rule: same record. What landed cost is is the definition. The Shopify landed-cost walkthrough and landed cost for a Shopify catalog are the storefront versions. Amazon FBA landed cost is the FC version.
The software test: can you open one inbound and see why the SKU cost $14.85 instead of $11.20? Estimates have to be replaceable when the freight bill arrives. Shared freight on a mixed container has to allocate on a rule you can repeat. Use allocate freight across SKUs if that is the weekly fight.
One Owner Per Field
Shopify may hold the catalog. Amazon may hold FBA quantities. The ERP may own purchasing, suppliers, and stock rules. Or the reverse. Both can work. Two writers cannot.
Build the field list: SKU, cost, price, inventory owner, order status. A paid Shopify order should not enter purchasing twice because two systems read different statuses. An FBA inbound should not increment Shopify available. Name error handling. Name who can pause sync.
Messages Next To The Order They Change
Most factories live in WeChat. Keep the thread, or a dated summary of it, on the PO. Supplier management software is the factory-facing version. Supplier portal software is the record version: what has to live on the order so a second person does not hunt chat.
Shopify, Amazon, And Woo Do Not Share A Warehouse
The same SKU can be healthy on one channel and dead on another. That is not a reporting bug. It is three fulfillment paths sharing one factory order.
| Channel | The Number People Trust | The Number They Should Trust | The Failure |
|---|---|---|---|
| Shopify | Available on the product | Available minus reserved, plus honest inbound | Reorder from a listing that is already committed |
| Amazon FBA | "In stock" in Seller Central | Sellable vs inbound vs reserved vs unfulfillable | Buy twice, or advertise units Amazon has not received |
| WooCommerce | On-hand in the store | On-hand minus holds and unsellable | Oversell a customized catalog that syncs late |
Test one paid order, one refund, one FBA inbound, one shared freight bill, and one factory date change. If the team cannot trace those five, the integration is a logo wall. Shopify's ERP comparison for merchants is honest about the storefront not being the whole business. Treat Amazon and Woo the same way.
Keep the templates until a system has earned the right to replace them. A neglected ERP is worse than a dated sheet everyone still opens.
ERP Vs Connector Vs The Admin Plus A Sheet
| System Type | Best At | Usual Gap | Use It When |
|---|---|---|---|
| Shopify / Amazon / Woo admin + sheet | Channel orders and a visible buy list | Documents and import cost | One person, simple POs, one dominant channel |
| Direct connector | A defined set of objects into an ERP | Supplier files, landed cost, failed jobs | Stable catalog, simple order flow |
| Middleware / OMS | Routing, translation, many channels | PO and freight as first-class objects | Amazon and Shopify use different states |
| Broad ERP (NetSuite, Business Central, SAP, Acumatica) | Finance, inventory, purchasing, entities | Setup, and product-level import cost unless you build it | You already have formal finance needs |
| Focused importer / ecommerce system | Channel orders, suppliers, documents, cost | Fewer industrial and multi-entity processes | The daily work is inbound execution and margin |
Shopify documents connectors for NetSuite and Business Central. Amazon has the same connector pile. Integration alone should not decide the choice. Every option above can show a Shopify or Amazon logo. Choose the narrowest model that handles your real exceptions.
A paid order, a refund, a return, an FBA inbound, and a factory date change: those are the test set. Shopify's migration guidance still applies: check imported price, weight, and inventory, and run test transactions before launch. Do the same in Seller Central and Woo.
If the books need a final accounting home, review landed cost in QuickBooks before you decide where adjustments live.
Where A Focused Importer System Fits
SupplyAutomate is not NetSuite. It is not SAP. It is built for Shopify, Amazon FBA, and WooCommerce importers who want purchase orders, supplier documents, and landed cost in one workspace.
Upload the invoice, packing list, and freight bill. Match them to the PO. See the SKU cost and what is still late. Orders from the connected channels stay tied to the same SKU. That is the work between the sale and the supplier: the gap the Shopify admin, Seller Central, and most ERPs leave in a spreadsheet.
It will not replace a controller's ERP. Multi-entity consolidations, shop-floor MRP, a global chart of accounts: look at the broad-ERP row. You still need clean SKUs and honest dates.
Start with one recent PO and its documents. Not a catalog import. The supplier management comparison is the factory-record version. The supplier portal page is what has to live on the order. The profit margin calculator sits beside the cost record. It does not replace it.
FAQ
What Is ERP For Ecommerce?
Software that connects online orders with inventory, purchasing, fulfillment, suppliers, and finance. The useful version follows each SKU from the factory PO to the customer sale on Shopify, Amazon FBA, or WooCommerce, and separates available stock from inbound or committed units. A storefront connector by itself is not that.
Do Shopify And Amazon Sellers Need The Same ERP?
They need the same objects: PO, documents, dates, and unit cost. They do not need the same warehouse model. Shopify available, FBA sellable, and Woo on-hand are different numbers. Buy the system that can hold all three without pretending they are one bin.
Can One System Cover Shopify, Amazon FBA, And WooCommerce?
Some ecommerce and importer systems do. Confirm the exact integrations before you buy. Shared order, supplier, document, and landed-cost processes matter more than a logo wall of channels. A broad ERP can do it too, usually as a project.
What Is Landed Cost In Ecommerce?
The total cost of getting a unit ready to sell, not only the supplier invoice. Freight, duty, customs charges, inspection, inbound prep. Use it to price and reorder on every channel. Keep referral and fulfillment fees in the margin view, not mixed into inventory unless your accountant says otherwise.
When Is A Full ERP The Wrong First Buy?
When you do not have a controller, entities, or a finance team that will own the rollout, and the actual pain is a freight bill and a date that never reached the SKU. A suite is the right project when the books need one. Documents, dates, and unit cost do not require that project first.
Three storefronts plus a stale unit cost is not an ERP. Entities, a general ledger, and a controller who will not accept a sidecar still mean a real ERP project. Documents, dates, and unit cost do not. SupplyAutomate is built for the shipment record across Shopify, Amazon, and Woo. The landed cost calculator will show which number you have been reordering on.