Cin7 + Go Fig
Connect Cin7 inventory and order management to Go Fig for landed-cost margin, working-capital, and channel profitability analysis.
Cin7 (Core and Omni) is the inventory and order-management backbone for ecommerce, B2B wholesale, and omnichannel brands that outgrew QuickBooks Items but are not ready for a full NetSuite deployment. It tracks stock across warehouses, 3PLs, and sales channels; landed cost on POs; bill of materials for light assembly; and order flow through Shopify, Amazon, EDI, and B2B portals. The analytics gap is predictable: Cin7 reports are channel-by-channel lists, and the join back to accounting for real gross margin requires manual reconciliation. Go Fig connects to Cin7 via its API (API v1 for Core, v2 for Omni), lands every stock movement, PO, sales order, credit note, and landed-cost posting in the Financial Intelligence Graph at SKU-and-location grain, and joins the inventory ledger to the accounting ledger so Celeste and your finance team can answer true landed-cost gross margin, working-capital tied up by SKU, channel profitability net of fulfillment cost, and stockout-risk-weighted revenue without hand-building another spreadsheet each week.
Key facts
- Products
- Cin7 Core (formerly DEAR) and Cin7 Omni
- Grain
- SKU, location, and stock-movement level
- Landed cost
- Freight, duty, handling preserved per PO
- Channels
- Shopify, Amazon, EDI, B2B portals joined
- Sync cadence
- 15-minute incremental on orders and stock
What you can do with Cin7 data in Go Fig
True landed-cost gross margin
Combine Cin7 landed-cost postings (freight-in, duty, handling, insurance) with SKU-level sell-through so finance sees gross margin that reflects the actual cost of bringing inventory to the shelf, not the unit cost the buyer quoted six months ago.
Working-capital and inventory aging
Track days of inventory on hand, aging by SKU, excess-and-obsolete exposure, and the cash tied up per product family. A CFO-level view that Cin7's inventory reports hint at but do not assemble into a working-capital narrative.
Channel profitability net of fulfillment
Join Cin7 sales orders to channel-specific fees (marketplace commissions, fulfillment cost, returns rate) so Shopify-direct, Amazon FBA, and B2B wholesale are compared on the same net-contribution basis rather than gross revenue.
Data available from Cin7
Go Fig extracts and normalizes the following data from your Cin7 account:
How to connect Cin7
Generate Cin7 API credentials
In Cin7 Core, open Settings, Integrations, API v1 or v2, and issue a new Application Key paired with your Account ID. In Cin7 Omni, generate a Connection ID and API key under the same area. Use a dedicated service identity rather than a named user so key rotation does not affect anyone's login.
Select accounts, warehouses, and channels to sync
Brands running multiple Cin7 accounts (for example, a US and an AU entity) connect each separately. Pick which warehouses, locations, and sales channels should flow through; most customers sync everything because channel profitability comparisons require the full set. Historical backfill is typically 2 to 3 years, which covers seasonality and inventory-aging analysis.
Reconcile costing method and landed-cost postings
Cin7 supports FIFO, FEFO, or moving average depending on account configuration. Go Fig preserves Cin7's costing output as the book value and also exposes the underlying stock movements so you can recompute margin under a different method if finance needs to for management reporting. Landed-cost components (freight, duty, handling, insurance) are pulled as typed columns rather than rolled into unit cost so the composition is visible.
Join to accounting and channel data
Cin7 typically posts summarized journal entries into QuickBooks, Xero, NetSuite, or another GL. Go Fig keeps both the Cin7 item-grain ledger and the posted accounting GL so you can trace a consolidated COGS figure back to the SKUs that drove it. Shopify, Amazon, and EDI channel feeds are joined where present so channel net margin nets out fulfillment and commission cost.
Authentication: API key authentication against Cin7's REST API. For Cin7 Core (DEAR lineage), Go Fig uses the Account ID plus Application Key header pair generated under Settings, Integrations, API. For Cin7 Omni, a Connection ID and API key are issued from the same area. Keys are scoped per Cin7 account and can be rotated independently; Go Fig supports read-only key scopes where Cin7 exposes that permission level.
Common Questions About Cin7 Integration
Does Go Fig support both Cin7 Core and Cin7 Omni?
Yes. Cin7 Core (formerly DEAR Systems) and Cin7 Omni are built on different API foundations and schemas, but Go Fig normalizes both into the same downstream data model. Flows and dashboards are portable across the two products, which matters for brands in the middle of migrating from Core to Omni or operating both for different divisions. If you also run Cin7 POS, that data comes through the same connector.
How is landed cost handled?
Cin7 lets you attach freight-in, duty, handling, and insurance to a PO and allocate them across received SKUs. Go Fig preserves each landed-cost component as a typed column on the PO and the receiving stock movement, rather than collapsing them into a single unit cost. That means Celeste can report gross margin gross of freight, after duty, after all landed cost, or under an alternative allocation method without losing the underlying detail.
How does Go Fig represent assemblies, kits, and bills of material?
BOMs and assembly jobs are pulled as first-class entities. When a kit ships, Go Fig retains both the parent SKU at sale and the component SKUs at cost, so margin reports can be built at either grain. Assemblies with routing (light manufacturing) are joined to their component consumption and labor cost where Cin7 tracks them, which is the pattern brands with in-house assembly or contract pack runs typically need.
Can inventory data be reconciled back to accounting on a consolidated basis?
Yes. Cin7 posts summarized inventory, COGS, and purchasing entries into the connected accounting system (QuickBooks, Xero, NetSuite). Go Fig keeps both the Cin7 item-grain ledger and the accounting-side posted GL so the consolidated COGS line on the P&L ties back to the SKUs, warehouses, and channels that drove it. Reconciliation variances (posted GL versus recomputed inventory ledger) are surfaced as a diagnostic so month-end close sees them quickly rather than after a surprise audit finding.
How current is Cin7 data inside Go Fig?
Orders, stock movements, and POs sync on a 15-minute incremental cadence anchored on Cin7's LastUpdatedOn timestamps. Product master and BOMs sync hourly because they change less often. Full reindex runs nightly to catch backdated adjustments, including negative stock corrections that finance often posts after a cycle count. Close-week on-demand sync is available for controllers who want the freshest inventory ledger before posting month-end COGS.
Related Operations integrations
Other systems Go Fig connects into the Financial Intelligence Graph, often alongside Cin7.
