Build a landed-cost stack that reaches the ledger

A product can look profitable in an ecommerce dashboard and still lose money after ocean freight, customs duty and fulfilment costs are counted. The fix is not one more report. It is a controlled path from purchase order and shipment evidence to inventory valuation, the general ledger and channel-level margin reporting.

Consider an importer selling two products through its own online store and a marketplace. Its freight invoices arrive after the goods, customs charges sit with a broker, and the third-party logistics provider (3PL) reports stock and fulfilment activity separately. This is a common operating pattern, not a claim about any specific company. The stack below makes those records usable without assuming that every system connects automatically.

1. Set the records and owners

Start by identifying the source of truth for each fact. The ecommerce and order system records orders, discounts and sales channel. The inventory or purchasing system records purchase orders, receipts and product quantities. Freight forwarder and customs broker documents support transport and duty charges. The 3PL provides receipts, shipments, returns and stock adjustments. The accounting ledger holds the financial balances and period-end entries.

Give each record an identifier that can travel through the process: purchase order, shipment or container reference, SKU, entity and currency. If a provider cannot include those fields, agree a mapping table and owner for matching its files. A spreadsheet can be a workable bridge at low volume, but it needs version control, review and a named person responsible for updates.

2. Build the landed-cost calculation

For each shipment, assemble the supplier invoice, freight and insurance charges, customs duty and other eligible costs under the company’s accounting policy. Decide how shared costs will be assigned across products. Weight may fit freight; customs value may fit duty; unit count may fit a simple shipment of similar goods. The basis should reflect the cost and be applied consistently, not selected after seeing which product needs a better margin.

For example, if a shipment contains two SKUs and the freight charge is shared, allocate it by chargeable weight when weight drives the carrier’s bill. Allocate duty using the customs values and rates applicable to the goods. Then calculate a per-unit amount for each SKU: its assigned eligible shipment costs divided by the quantity received. Document the source amounts, allocation basis, exchange rate and any estimate used. Confirm the treatment of costs with the responsible accounting adviser; requirements and policies can differ.

Do not bury marketplace commissions, payment processing charges or outbound fulfilment fees in product landed cost simply to produce one “all-in” number. Keep those channel and selling costs distinct in reporting. That lets managers compare product economics across channels and see whether a price, freight or fulfilment change caused the margin shift.

3. Make the inventory valuation software integration practical

The integration does not have to mean a live software connection. It means defined, reconcilable handoffs. The inventory record should carry quantities and the approved unit cost into the accounting ledger, while the shipment schedule explains how that cost was built. Where systems support exports or integrations, test that SKU, entity, currency, dates and references survive the handoff. Where they do not, use a controlled import or journal process with totals and supporting files attached.

Choose and document an inventory valuation method that fits the business and applicable accounting requirements, then apply it consistently. Decide how late freight or duty invoices will be treated: for example, whether an estimate is accrued at receipt and trued up when the invoice arrives. Define who approves the adjustment and how it affects remaining stock versus goods already sold. Avoid silently changing unit costs in closed periods.

4. Reconcile the 3PL financial integration stack

At each close, reconcile opening 3PL units plus receipts, less shipments and other authorised movements, to closing units. Match receipts to purchase orders and shipments to sales or transfer records. Investigate timing differences, damaged stock, returns and write-offs rather than forcing a plug to make the totals agree. Reconcile the inventory subledger value to the ledger control account, with a bridge for in-transit goods and cost adjustments.

This is where the finance operating model matters as much as the software. CFO World is a CA-led outsourced finance and virtual CFO practice that provides accounting, compliance, reporting and strategic finance services. Its stated delivery structure spans CFO oversight, controller and reporting, accounting and compliance execution, and specialist support. A business could scope those responsibilities around its close calendar and inventory controls; it should agree the system handoffs and accountable owners rather than assume a particular direct integration is included.

5. Turn the records into channel economics

Report gross margin by SKU and sales channel using net sales less the product cost under the chosen valuation method. Then show channel fees, fulfilment and returns separately. Include a short reconciliation from operational quantities to ledger balances, plus a list of open invoices and estimates. That gives operators a view they can act on and gives finance a trail to review. For evidence discipline more broadly, CFO World’s guide to keeping audit evidence attached during a pre-audit clean-up offers useful context.

The trade-off is real: more detailed allocations improve product and channel comparisons, but require better shipment data and more review time. Start with a defensible allocation basis, a monthly reconciliation and a clear owner for exceptions. Add automation only where it removes repeated handling without obscuring the evidence behind the number.