Inventory truth
Warehouse-aware stock with reservations, movements, and exception accountability.
Features
Capabilities are organized by how stock, cost, cash, and contribution move from purchase order through close.
Purchase, receive, land cost, sell, fulfill, return, fees, payout, contribution, and close.
Warehouse-aware stock with reservations, movements, and exception accountability.
Landed unit cost and COGS that survive late invoices and returns.
Settlements and journals with review boundaries and source lineage.
Catalog, purchasing, document intake, receiving, and landed cost.
One catalog of SKUs, variants, costs, and prices across connected channels.
How it works
Maintain products and variants with shared cost and pricing fields used by inventory, orders, and accounting.
Business consequence
Sales and receipts reference the same product identity.
Supplier invoices and receipts become reviewable receiving drafts.
How it works
Extract line items into drafts with source evidence; nothing posts without human approval.
Business consequence
Purchase evidence enters the ledger without silent automation.
Receive purchase orders and allocate freight, duty, and handling onto unit cost.
How it works
Draft → review → post receiving with cost allocation drivers on each unit.
Business consequence
Inventory value and COGS start from the configured landed-cost allocation.
Reorder from velocity, cover, and shortage signals—not guesswork.
How it works
Surface low stock, days of cover, and purchasing handoff from the same inventory truth.
Business consequence
Purchasing decisions use reservation-aware availability and backlog.
Match ordered, received, and invoiced quantities with variance control.
How it works
Track accruals, price variance, and approval states on supplier evidence.
Business consequence
Purchasing closes with accountable AP and inventory value.
Inventory truth, warehouses, transfers, counts, lots, and exceptions.
On-hand, reserved, committed, incoming, and available stock per warehouse.
How it works
Event-backed movements with full history—no silent stock mutation.
Business consequence
Operators see sellable availability with provenance.
Returned units quarantine, inspect, restock, or write off with cost impact.
How it works
Return disposition flow that keeps damaged stock out of sellable availability.
Business consequence
Refunds and restocks reverse inventory and contribution correctly.
Allocation shortfalls stay visible per order, product, and warehouse.
How it works
Record shortages from the inventory ledger when demand exceeds availability.
Business consequence
Restock priority follows recorded customer and channel demand.
Hold and sell stock from multiple locations with per-location truth.
How it works
Warehouse-aware quantities, reservations, and channel mappings.
Business consequence
No global average stock that hides location reality.
Move inventory between warehouses with in-transit custody.
How it works
Transfer documents track origin, destination, and goods in transit.
Business consequence
Location custody stays traceable during movement.
Correct records with movement-safe variance baselines.
How it works
Physical counts post atomically against the counted baseline for the selected locations.
Business consequence
Adjustments do not corrupt concurrent sales activity.
Scan to receive, pick, and count with fewer typing errors.
How it works
Workstation and mobile scan flows keyed to SKU and location identity.
Business consequence
Warehouse actions attach to the correct unit and place.
Trace batches, expiry, and individual serial units through the ledger.
How it works
Lot/serial identity rides on receipts, sales, returns, and quarantine.
Business consequence
Warranty, recall, and RMA workflows keep unit-level history.
Channels, orders, fulfillment, wholesale, and shipping handoffs.
Orders from every connected channel in one operating queue.
How it works
Normalize channel orders into allocation, fulfillment, and return workflows.
Business consequence
Fulfillment and COGS attach to the same order identity.
Shopify catalog, inventory locations, orders, refunds, and payouts in one ledger.
How it works
Map Shopify products and locations; ingest orders and settlements into inventory and accounting consequences.
Business consequence
Shopify operations share stock truth and product contribution margin.
Etsy products, inventory, orders, and fees on the same stock and margin ledger.
How it works
Ingest Etsy order and fee objects into shared inventory and contribution workflows.
Business consequence
Etsy sales do not live in a separate spreadsheet island.
WooCommerce catalog, stock, orders, and fulfillment connected to cost truth.
How it works
Sync store objects into the multichannel order and inventory model.
Business consequence
Self-hosted store operations close with the same accounting path.
Amazon marketplace catalog, inventory, orders, fees, and settlements in one system.
How it works
Map marketplace SKUs and ingest order and settlement data for margin and stock.
Business consequence
Amazon product contribution is comparable with connected-channel results.
Best Buy USA and Canada offers, orders, and payout settlement ledgers.
How it works
Marketplace offer and order objects flow into inventory allocation and settlement reconciliation.
Business consequence
Best Buy operations share the same stock and close path.
One stock pool with channel SKU and warehouse mappings across marketplaces.
How it works
Reservation-aware availability publishes from the shared inventory ledger.
Business consequence
Channels sell from controlled availability, not disconnected counts.
Allocate, pick, pack, and ship from a unified multichannel order queue.
How it works
Fulfillment status updates inventory commitment and COGS recognition.
Business consequence
Shipments reduce stock and book cost from the same event trail.
Wholesale catalogs, buyer groups, terms, and invoice workflows on inventory truth.
How it works
Portal ordering with price lists, credit terms, and inventory allocation.
Business consequence
Wholesale demand competes fairly with retail channel demand.
Carrier and 3PL handoffs with tracking and attributable shipping cost.
How it works
Exchange fulfillment status and shipping costs into contribution margin.
Business consequence
Fulfillment partners do not erase landed cost or margin visibility.
BOMs, assemblies, and cost roll-up into finished goods.
Define multi-level BOMs and kits with component cost roll-up.
How it works
BOM structure links components, substitutes, and finished goods identity.
Business consequence
Built products inherit component cost into inventory value.
Consume components and produce finished goods with cost roll-up.
How it works
Assembly orders post component consumption and finished stock in one movement set.
Business consequence
Manufacturing stock and cost stay ledger-consistent.
Payouts, multicurrency, contribution margin, and accounting journals.
Preserve native amounts and normalize reports to home currency.
How it works
Rate provenance with home-currency views at the reporting layer.
Business consequence
Cross-border operations keep FX history with inventory and margin.
Map commerce consequences into journal-ready accounting close.
How it works
Account mapping for inventory value, COGS, fees, and settlements.
Business consequence
Books receive reviewed commerce outcomes—not disconnected exports.
Marketplace payouts land as gross, fees, refunds, tax, and net cash.
How it works
Settlement legs link back to orders for residual resolution.
Business consequence
Cash received reconciles to sales activity.
Decompose payouts into revenue, fees, refunds, and taxes for the chart of accounts.
How it works
Per-line settlement classification with accountant-ready journal structure.
Business consequence
Close does not collapse taxes and fees into a single opaque amount.
Net sales less landed COGS and attributable channel, payment, fulfillment, and return costs.
How it works
Snapshot unit cost at sale and attach attributable operating costs per SKU and order.
Business consequence
Operators see product contribution—not company net income.
Enter historical product costs by date range, then post real cost onto past sales without rewriting history.
How it works
A cost period is an explicit assertion of unit cost for a date range. The run lists which sales will get real cost and which will not, and why. Posting adds new cost rows dated when you run it, referencing the original sales.
Business consequence
You can catch up old estimated sales, then lock those periods so later edits cannot quietly change the story.
Inventory, valuation, margin, and posted tax activity with source lineage.
How it works
Reports read posted ledger consequences, not spreadsheet snapshots.
Business consequence
Reviews and filings start from the same operating record.
Tenant isolation, audit history, API, AI assist, and migration cutover.
Programmatic access for your own systems and automation.
How it works
Scoped keys and object/event surfaces for inventory and order integration.
Business consequence
External systems connect without bypassing review boundaries.
Sensitive actions record actor, action, time, and outcome.
How it works
Security-relevant mutations and login activity write durable history.
Business consequence
Corrections and access remain accountable.
Authenticated workspace context scopes customer-data access, with database policies adding fail-closed enforcement to customer-facing records.
How it works
PostgreSQL row-level security protects the public application schema; platform and canonical paths retain explicit tenant-scoped authorization.
Business consequence
Customer records are evaluated against explicit workspace boundaries across application and database controls.
Import openings, reconcile, activate cutover, then connect channels.
How it works
Migration-first path validates stock and financial openings before go-live.
Business consequence
Cutover starts from reconciled truth, not empty defaults.
Explain exceptions and propose reviewable drafts without autonomous financial posts.
How it works
AI suggests with evidence; humans approve before inventory or money moves.
Business consequence
Automation accelerates review without silent ledger posts.
Map catalogs, import openings, validate, reconcile, and cut over under control.
How it works
Structured cutover checklist, field mapping, and reconciliation before channel activation.
Business consequence
Operators switch systems with known balances and exceptions.
Cash, stock, and SKU contribution for channel decisions.
Purchase through return workflows with controlled availability.
Landed cost through journals and reconciliation.
Commerce, accounting, logistics, and marketing platforms share inventory, cost, and settlement identity.
Layered tenant isolation and audit history protect customer records. AI and parsers propose drafts only—humans review before inventory or money posts.
No. Inventory is connected to landed cost, multichannel orders, contribution margin, payouts, and accounting close.
Each integration is presented with the objects it exchanges and the operational consequences for inventory, cost, and close.
Net sales less landed COGS and attributable channel, payment, fulfillment, and return costs—not company net income.
Document intake and sensitive mutations create reviewable drafts; posting is a human decision with audit history.
Book a migration review to map inventory, cost, and close to your stack.