One ledger for every channel.

Parts List

Five ways multichannel selling breaks a simple stack.

None of these are exotic problems. They are what happens when a business that sells in more than one place is still running on tools built for a business that sells in one.

1. 01

   Inventory is counted channel by channel

   Amazon shows one stock number, Shopify shows another, the wholesale spreadsheet shows a third, and none of them agree with what is actually on a shelf. A single SKU sold in four places needs four honest numbers reconciled to one truth, not four separate guesses.

2. 02

   FBA and FBM stock are not the same pool

   Units sitting in an Amazon fulfillment center are not available to sell on Shopify, and units in a self-fulfilled warehouse are not available to Prime shoppers. Selling from the wrong pool means an oversell, a cancelled order, or a customer waiting on a shipment that was never coming.

3. 03

   Marketplace fees get lost between the settlement report and the books

   A marketplace settlement report nets referral fees, fulfillment fees, advertising spend, and returns against gross sales before the money ever lands in the bank. If the accounting system only sees the net deposit, nobody can see true product margin, and month-end becomes a manual reconciliation project against a PDF.

4. 04

   Returns are a different process on every channel

   A marketplace return, a Shopify return, and a wholesale return each carry their own paperwork, their own restocking decision, and their own credit. Handled outside the core system, a return is a spreadsheet row that never quite makes it back into the stock count or the customer's account balance.

5. 05

   3PLs and warehouses run on their own clock

   A third-party warehouse ships an order, marks it fulfilled in its own system, and the seller's own inventory count does not move until someone remembers to update it. The gap between what a 3PL says it shipped and what the seller's books say is on hand is where stockouts and phantom inventory both live.

Parts List

How the channels actually connect.

Amazon, Shopify, WooCommerce and ShipStation connect to ERPNext through integration apps and APIs — there is no single native connector that covers all four. Here is what each one actually is, with a link to the source.

Parsimony's own ShipStation integration is open source: MIT-licensed, built on Frappe and ERPNext, and public on GitHub. It syncs multiple ShipStation accounts into one ERPNext instance, maps each store to a company, warehouse, cost center, and account heads, fetches products, orders, and shipments on a schedule, flags stores connected to the Amazon marketplace, and generates shipping labels where enabled. It is the same instinct behind Sourcing Goat, Parsimony's own product-sourcing tool: supplier, quote, and shipment records live as data in ERPNext on the Frappe framework — direct proof that Parsimony's ERPNext work runs in production, not only in a sales deck.

Cutover Plan

A multichannel go-live, in order.

Typically weeks, not quarters — the same target Parsimony publishes on the Cloud ERP page. A multichannel seller adds channel mapping and reconciliation steps to that plan; the six moves below are the shape of it.

1. 01

   Map the channels

   List every channel, every warehouse and 3PL, and every SKU with variants. Decide which stock pools are separate (FBA, FBM, wholesale) and which item attributes need Item Variants.

2. 02

   Configure items and warehouses

   Build the Item master with variants for size, color, or bundle, and create a Warehouse per stock pool. This is the structure every later order and return will post against.

3. 03

   Connect the channels

   Install and configure the integration app for each channel in scope — Amazon and Shopify through Frappe's ecommerce_integrations app, ShipStation through Parsimony's own app, WooCommerce through the community app that fits — and map each store to its company, warehouse, and accounts.

4. 04

   Import orders and reconcile opening stock

   Bring in open Sales Orders and a snapshot of stock by warehouse, then reconcile every warehouse's opening balance to the channel's own inventory report before anything ships from ERPNext.

5. 05

   Set up fee accounting and returns

   Configure how each channel's fees post to the chart of accounts, and confirm the Sales Return flow for that channel — return Delivery Note, return Sales Invoice, or both — before the first live return arrives.

6. 06

   Run a parallel week, then cut over

   Take a week of real orders through the new system alongside the old one, compare stock and revenue, then freeze the spreadsheets and go live.

Exact scope — how many channels, how many warehouses, whether order history needs a backfill — gets written down before you sign, on the implementation services page.

01

Does ERPNext handle FBA and FBM stock separately?

Yes. A Warehouse in ERPNext can represent any storage location, including a nested tree — warehouse, room, row, shelf, bin. An Amazon FBA pool and a self-fulfilled FBM location are two separate warehouses under the same Item, each with its own stock ledger, so the system knows which pool a unit is actually sitting in before it lets you sell it again.

02

How does ERPNext account for Amazon and marketplace fees?

Referral fees, fulfillment fees, advertising spend, and returns all appear on a marketplace's settlement report netted against gross sales. In ERPNext, those fees post as line items or journal entries against the same chart of accounts as the rest of the business, so gross sales, fees, and net proceeds reconcile to the settlement instead of disappearing into one lump deposit.

03

How do returns work across channels?

A Sales Return references the original Delivery Note or Sales Invoice and generates a return Delivery Note, a return Sales Invoice — what ERPNext's own documentation calls a Credit Note — or both. A return from Amazon, a return from Shopify, and a wholesale return all run through the same flow, so the stock count and the customer's credit both update from one transaction instead of a spreadsheet row someone has to remember to close out.

04

Do Amazon, Shopify, WooCommerce and ShipStation connect natively to ERPNext?

Amazon, Shopify, WooCommerce and ShipStation connect to ERPNext through integration apps and APIs, not one built-in connector. Frappe's own open-source ecommerce_integrations app currently supports Shopify and Amazon, installable from the Frappe Cloud Marketplace or via bench. WooCommerce connects through community-built Frappe apps rather than a Frappe-maintained core connector. Parsimony's own ShipStation integration is public and MIT-licensed: it syncs multiple ShipStation accounts into one ERPNext instance, maps stores to companies and warehouses, and fetches products, orders, and shipments on a schedule.

05

How is ERPNext different from spreadsheets plus QuickBooks for a multichannel seller?

Spreadsheets and QuickBooks were not built to hold one stock ledger across channels and warehouses, so a multichannel seller ends up reconciling channel exports by hand every month. ERPNext keeps items, warehouses, sales orders, landed cost, and returns in one system of record, with accounting posted from the same transactions the warehouse and the storefront already created — nothing gets re-keyed from a report.

06

How long does an ecommerce ERPNext go-live take?

Typically weeks, not quarters — the same target Parsimony publishes for every managed ERPNext engagement on the Cloud ERP page. A single-entity seller with clean item and order data follows the outline below; more channels, more 3PLs, or a long order-history backfill add time, and the written scope says how much before you sign.

Talk to an operatorRead the Cloud ERP explainer