Oracle NetSuite × Landed Cost Sync
NetSuite landed cost sync into Shopify Plus checkout: freight, duty, insurance, and handling flow into margin enforcement so checkout decisions use true cost.
Most Shopify Plus merchants who sync COGS from NetSuite only sync the item-level unit cost — the cost on the Item record. But unit cost is not true cost. True cost is landed cost: the unit cost plus inbound freight allocation, customs duty, insurance, broker fees, and warehouse handling. For imported goods, the gap between unit cost and landed cost is typically 18-35%. A product that costs $12 on the PO lands at $15.80 after freight, duty, and handling. If your checkout margin calculation uses the $12 number, you are overstating margin by 24% on every order containing that SKU. NetSuite has sophisticated landed cost tracking — it allocates freight, duty, and insurance across PO line items using configurable methods. But that landed cost data almost never makes it to Shopify. The standard sync flows (including most Celigo templates) only pull the base item cost field, leaving the landed cost components stranded in NetSuite. The result is a checkout engine that thinks it is enforcing a 25% margin floor but is actually approving orders at 18% true margin.
Agentis syncs the full landed cost from NetSuite — not just the unit cost field, but the allocated freight, duty, insurance, broker fees, and handling components that make up the true cost of each SKU. It reads NetSuite's landed cost allocation records and resolves the fully burdened cost per unit, then uses that number (not the base item cost) as the COGS input to the Shopify Plus checkout margin calculation. When a new container arrives and NetSuite recalculates the landed cost allocation — because freight was higher than estimated, or duty rates changed, or the broker invoice came in — Agentis picks up the updated landed cost and applies it to the next checkout. Your profit floor now reflects the real cost of putting that product on a shelf, not the cost of buying it at the factory gate.
Agentis reads NetSuite Landed Cost records via a dedicated RESTlet that resolves the fully allocated cost per item. It supports all three NetSuite landed cost allocation methods: by quantity, by value, and by weight. When inbound shipment records are updated in NetSuite (e.g., actual freight replaces estimated freight), the afterSubmit User Event trigger pushes the recalculated landed cost to Agentis. The landed cost is stored per item per lot/receipt, and at checkout Agentis resolves the cost using the same FIFO/weighted-average logic configured in your NetSuite costing rules. This ensures the checkout margin matches the cost your accountant would calculate.
Agentis reads all landed cost categories configured in your NetSuite instance: inbound freight, customs duty, insurance, broker fees, warehouse handling, and any custom cost categories you have defined. Each component is tracked separately in the Agentis cost model for reporting, but the sum is used as the COGS input at checkout.
NetSuite often records estimated landed costs when a PO is received and updates them when actual invoices arrive. Agentis uses whatever value is current in NetSuite. When the estimate is replaced by an actual, Agentis picks up the change and updates the margin engine. Orders confirmed between estimate and actual are flagged in the audit log for reconciliation.
Yes. For domestic items, the landed cost equals the item cost (no additional allocations). Agentis handles both cases seamlessly — it reads whatever landed cost NetSuite has calculated, whether that includes 6 cost categories or zero.
If you do not use NetSuite's native landed cost tracking, Agentis falls back to the item-level cost field (Average Cost, Last Purchase Price, or Standard Cost). You can still manually configure landed cost percentages per product category in Agentis as a stop-gap until you enable the NetSuite module.
The landed cost sync pipeline mirrors the cost-ingest model used for base COGS: a NetSuite RESTlet resolves the fully allocated landed cost per item, a User Event script emits an event whenever a landed-cost allocation changes, and the Agentis cache stores the result keyed by SKU and receipt. At Shopify Plus checkout, the margin engine pulls the current landed cost value — not the raw item cost — and uses it as the COGS input for the profit-floor evaluation. This is what makes landed cost Shopify enforcement real: the number the checkout sees is the same number your NetSuite landed cost allocation calculated, with no manual step between the two.
Feature
NetSuite Shopify Plus margin sync in real time. Agentis bridges the ERP-to-checkout gap so every order is evaluated against live COGS, not stale estimates.
Feature
NetSuite COGS automation for Shopify Plus. Automate COGS sync from your ERP, eliminate manual cost imports, and ensure every checkout uses current unit costs.
Free Audit — No Commitment
See exactly how much margin Agentis can recover for your store in 7 days — no commitment required.