Shopify says a product can still be sold, the warehouse export shows fewer cases, and a wholesale order is waiting for confirmation. CPG inventory management starts by making those quantities comparable: identify the same product, convert its selling packs, establish who owns it, and distinguish usable stock from units already promised or held.
Build a stock view by item, location, lot, ownership, and status, with a source timestamp on every balance. Keep incoming supply separate from physical stock. That gives you a reproducible answer to the immediate question, which units can support this order, without treating every number labeled inventory as interchangeable.
Choose the stock population before adding balances
Start with one product family and the locations involved in its next replenishment decision. Write down whether the report includes stock at the co-manufacturer, the third-party logistics provider, your own warehouse, and a retailer. A location can hold your goods without owning them, so location and ownership need separate fields.
Make the operations owner responsible for physical status definitions and have finance approve ownership rules. If a distributor has bought the goods, its inventory may matter for channel analysis without belonging in your owned-stock total. Retain that distinction rather than dropping the distributor feed or adding it to the warehouse balance.
The CPG ERP software evaluation covers the separate decision of choosing an operating system. Keep a working ERP when the immediate failure is a mismatch among its records and external feeds. Replacing the transaction system does not itself settle which quantities the report should include.
Match product identifiers and dated pack conversions
Create a crosswalk between the ERP item, Shopify variant, warehouse SKU, and any customer-specific code. Include the effective dates and the packaging unit attached to each identifier. An identifier reused for a different case size should produce a review exception, because a timeless mapping would rewrite historical quantities.
Suppose a hypothetical feed contains 24 cases of a product packed 12 each. That represents 288 each before reservations or holds. Another feed showing 288 each might describe the same stock; adding both would produce 576. Establish whether feeds are alternative views of one location or balances from distinct locations before summing them.
Store the original quantity and unit beside the converted amount. If a case changes to ten each, apply the approved conversion to records using that version. Do not average the two pack sizes or infer a conversion because the totals look close. Ask the item owner to approve the relationship.
Keep usable stock separate from physical and incoming stock
Shopify’s inventory state documentation distinguishes on-hand, available, committed, unavailable, and incoming quantities. On-hand comprises available, committed, and unavailable stock; incoming stock is separate until received. Those definitions provide a concrete example of why a physical balance can exceed what you can sell.
Build an explicit mapping for the warehouse’s status codes instead of assuming they use Shopify’s terms. Ask whether a quality hold is physical stock, whether a picked order remains committed until shipment, and when a transfer leaves one location and enters another. Preserve unmapped statuses as unknowns until an owner resolves them.
| Stock question | Evidence to retain | Failure to prevent |
|---|---|---|
| Is it here? | Location balance and timestamp | Counting an inbound shipment as received |
| Can it be sold? | Reservation and hold status | Offering quarantined units |
| Does it belong to the brand? | Approved ownership rule | Adding retailer-owned goods |
| Is it the same quantity? | Source unit and pack conversion | Adding cases to individual units |
Keep lot and expiry information where they affect usability. A balance can be available in a general stock report while a customer’s remaining-shelf-life requirement makes it unsuitable for that order. Record the customer rule (including its effective date) and report the exception without inventing missing lot dates.
Reconcile the same cut-off and explain the difference
Choose the cut-off for the comparison and keep each feed’s actual extraction time. If the ERP snapshot is from last night and the warehouse file includes this morning’s shipments, a difference may be caused by timing. Label it as a timing candidate until the intervening transactions explain the amount.
For a hypothetical check, start with 288 each at the warehouse. Remove 48 each shipped after the ERP cut-off and identify 12 each placed on hold. The current physical balance is 240 each and usable stock is 228 if no other reservations apply. Keep the shipment and hold records behind those changes.
Do not solve an unexplained difference by posting an adjustment merely to align two reports. Check missing receipts, transfers, unit conversions, duplicated feeds, and reservations first. The inventory reconciliation process explains the count-to-record investigation and approval path behind a justified correction.
Turn reconciliation into an owned review queue
Give each exception a reason, item, location, evidence link, owner, and next review time. Separate an identifier problem from a physical discrepancy and a stale feed, because they need different fixes. Keep the last verified balance visible beside a warning when new data is unavailable; never present it as current.
Review exceptions before the purchasing meeting rather than sending everyone a raw variance workbook. Start with stock that affects accepted orders or expiring goods. Record the decision and the evidence used so another person can understand why a transfer was proposed or why apparently available units were excluded.
Use the inventory planning workflow when the next question is how much to replenish. Reconciliation establishes trustworthy inputs. A reorder policy still needs approved demand assumptions, lead times, minimum quantities, and a person responsible for changing them.
Where Permute fits in recurring inventory reporting
Permute sells connected business data, custom applications, and governed analysis. We can scope a stock view from permitted Shopify and NetSuite records alongside approved warehouse exports. Your item mappings and status definitions govern how those records are compared, while the source quantity and evidence stay available for review.
We can reuse those definitions in a recurring exception report and a custom operations view. An inventory manager can inspect why a balance changed and which source is stale under current access permissions. Unmatched products and missing status mappings remain exceptions rather than becoming assumed stock.
Compare one product across its stock records
Bring permitted balances, units, and timestamps from the channels involved in one replenishment decision.
Keep release and replenishment decisions with their owners
We are not a forecasting engine, and a reconciled balance is not a demand forecast. This workflow reads source records; it does not promise to release held goods, change warehouse inventory, or place replenishment orders. Confirm supported connections and refresh intervals before relying on a recurring report.
Quality owners decide whether a lot can be released, finance owns accounting treatment, and operations approves the replenishment policy. A stock view can expose missing evidence and apply declared rules, but it cannot establish a physical condition that nobody has inspected or supply a lot date absent from the records.
Take a comparable stock position into the meeting
Match product identifiers and pack versions before combining quantities. Separate ownership, physical stock, usability, and incoming supply, then reconcile the same cut-off. Keep unresolved differences visible with an owner and evidence. Replenishment decisions can then use an explained stock position instead of competing totals.
Review a cross-channel inventory handoff
Bring the stock reports that disagree and the order decision waiting on them.
Questions about consumer-brand stock records
How should bundles be represented?
Retain the bundle SKU and its approved component quantities with effective dates. Determine whether the source has already reserved components for bundle orders before subtracting them again. Flag a missing component mapping rather than assuming the bundle and its components are independent stock.
Can retailer stock be included?
Include it in a separately labeled channel view when you have permission and a usable feed. Ownership rules determine whether it belongs in your owned balance. Keep the reporting period and freshness visible so sell-through analysis is not confused with warehouse availability.
What if a warehouse feed has no lot information?
Report that limitation at the item and location where it matters. Do not infer lot identity from a matching total. Obtain the missing records before using the view for an expiry-dependent or lot-specific decision.