To track in transit inventory open purchase orders, an importer first needs a shared status view—not a new reorder formula. Physical on-hand units, customer allocations, supplier-confirmed quantities, work in process, shipped units, partially received goods and unstarted PO balance are different states. Combining them into one “inventory” number can mislead a buyer in either direction: an order may be counted as available before it arrives, or inbound units may be omitted and a duplicate order released.
A useful view is dated, item-specific and tied to a destination warehouse. It shows what is physically usable, what is committed, what has been ordered, what has left the supplier or origin, what has been received and what remains unresolved. A supplier-confirmed quantity is not the same as stock available for immediate sale, and an estimated arrival date is not proof of receipt. The buyer should reconcile status and source records before deciding whether another PO is needed.
Separate inventory states before you track in transit inventory open purchase orders
Start by agreeing what each status means in the buyer’s system. “On hand” should refer to stock recorded at a physical or controlled warehouse location according to the company’s method. “Available” may exclude reserved, allocated, damaged or quality-hold units. “Allocated” represents quantities committed to customer orders or internal projects. These terms can differ between software, warehouses and companies, so document the local definitions before comparing reports.
An open PO also has sub-states. It may be drafted but not sent, sent but not acknowledged, acknowledged by the supplier, scheduled, in production, packed, ready for pickup, shipped, partly received or closed. The buyer should not treat all open PO lines as equal. An unconfirmed PO does not prove that the supplier has accepted the item, quantity or schedule. A confirmed order still does not mean the goods are physically available to ship to customers.
“In transit” should likewise have a clear basis. It may refer to goods that left the supplier but are not yet received at the buyer’s destination. A shipment in preparation, awaiting pickup or held at origin may be tracked separately. A system or carrier may use its own definitions. The buyer should retain the source status and timestamp instead of collapsing every milestone into one label.
The distinction matters for imported bathroom and home-storage hardware. One PO line may cover multiple SKUs, cartons or ship dates. A container may include multiple suppliers or destinations. One SKU can be split across production lots and receipts. A master order number alone is not enough for a buyer to know which product quantity can be allocated.
Oracle NetSuite documentation explains inventory optimization using item-location and demand/supply information, while logistics systems may represent order lines that are in transit before destination receipt. These are software-specific examples that support a practical point: the buyer must distinguish SKU and location, and separate inbound from received quantities. The systems’ calculations or labels are not universal definitions and should not be adopted without understanding their configuration.
A status vocabulary for purchase teams
A simple working vocabulary can make communication clearer:
- On hand: physically recorded at a named warehouse or location.
- Available: on hand less quantities reserved or otherwise unavailable under the buyer’s rules.
- Allocated/committed: tied to customer orders, projects, samples or internal demand.
- PO submitted: buyer issued an order but supplier acknowledgment is not recorded.
- PO acknowledged: supplier confirmed the order details under the company’s process.
- In production: supplier reports that the relevant quantity entered production; the source and date should be recorded.
- Ready to ship: supplier or forwarder reports goods prepared for dispatch, with pickup still to confirm.
- Shipped/in transit: goods have left the stated origin and are moving toward the stated destination according to available records.
- Partially received: a portion reached the destination and was recorded; balance remains open.
- Quality hold or damaged: physically present but not yet usable or saleable under buyer rules.
- Closed: PO line balance and receiving status reconciled according to the buyer’s process.
These labels are starting points, not mandatory system statuses. Define how each one is assigned, who updates it and what evidence supports it. If a supplier says “complete,” ask whether that means production complete, packing complete, inspection complete or goods handed over. Similar words can refer to different milestones.
Build a dated status view by SKU and destination
The view should use a row that can be traced to an item and location. For each SKU, include item description or revision, destination warehouse, on-hand quantity, allocated quantity, quality-held quantity, open PO lines, shipped balance, partial receipts and a last-confirmed date. If products are sold as sets or kits, record the unit basis and whether the frame, fasteners and packaging are complete.
A buyer may keep the information in an ERP, a spreadsheet, a shared portal or a controlled report. The tool is less important than the definitions, source links and update ownership. Do not claim that Koitor operates the buyer’s inventory software or controls the buyer’s warehouse. The supplier can provide its own order and shipment information; the importer combines it with its own records.
| SKU / destination | State | Quantity | Status source | Last confirmed | Exception owner |
|---|---|---|---|---|---|
| Example SKU A / Warehouse 1 | On hand | Illustrative only | Warehouse record | Date and time | Inventory planner |
| Example SKU A / Warehouse 1 | Allocated | Illustrative only | Order system | Date and time | Sales operations |
| Example SKU A / Warehouse 1 | Supplier-confirmed PO | Illustrative only | Supplier acknowledgment | Date and time | Purchasing |
| Example SKU A / Warehouse 1 | Shipped/in transit | Illustrative only | Shipment document or carrier update | Date and time | Logistics |
| Example SKU A / Warehouse 1 | Received against PO line | Illustrative only | Receiving record | Date and time | Warehouse |
The sample table uses no real quantities; an actual team should populate it from its own controlled records. Include a source and date with each status. A quantity without a timestamp can be stale even if it was once correct. A supplier email from last month may not reflect a rescheduled production line, partial shipment or updated balance today.
Use a consistent item identifier. Product names can vary between a purchase order, packing list, warehouse system and customer-facing catalog. The SKU, supplier item code, drawing revision or another controlled cross-reference should connect them. If the buyer’s item code differs from the supplier’s, maintain a mapping table and review it before reorders.
Destination matters because one inbound quantity may be assigned to a particular warehouse, customer or project. A buyer with several destinations should not treat stock headed to one location as immediately available at another without a transfer plan. Customs, carrier, ownership and terms questions depend on the buyer’s records and agreements; the status view should not infer those from a generic “in transit” label.
Use dates that describe an actual event
Record the event date separately from the forecast date. “Supplier confirmed on October 30” is different from “estimated arrival November 20.” The first is a communication timestamp; the second is a forecast that can change. If the date is estimated, label it as such and preserve its source. Avoid presenting an estimate as a guarantee.
For each inbound line, track several dates when available: buyer PO date, supplier acknowledgment date, latest supplier update, inspection or release date if relevant, shipment handoff date, estimated arrival, actual receipt and closure. Not every order will have all those events. Use “not provided” or “not applicable” rather than inventing an event.
Handle partial receipts and split shipments
A PO line can be fulfilled in more than one shipment or receipt. The buyer should reconcile the original ordered quantity, confirmed quantity, quantity shipped, quantity received, rejected or held quantity and remaining balance. Make sure each transaction references the same item and order line. A partial receipt does not necessarily close the PO.
A simple example can use symbols rather than fake business data:
- Q = quantity ordered on the PO line.
- S1 = first shipped quantity.
- R1 = first quantity received and recorded.
- S2 = subsequent shipped quantity.
- R2 = subsequent receipt.
- B = open balance after the recorded receipts, subject to holds or approved changes.
The buyer should reconcile these values using its own documents and system rules. A difference between shipped and received quantity should be investigated; it should not be silently treated as loss or as available stock. Verify whether the shipment was split, the receiving record is incomplete, units are held for inspection, or a supplier amendment changed the ordered quantity.
A partial receipt can create double-counting if the original PO quantity remains listed as open while the received units are also added to stock. It can also create an omission if the system closes a line after the first receipt while a second shipment remains in transit. The buyer needs line-level status and a remaining quantity that reflects the actual order record.
If one container consolidates multiple SKUs, map the carton tally and shipment documents to each SKU. A shipment total is not enough if the buyer needs to decide whether one particular item is available. The multi-supplier consolidation readiness guide covers shipment coordination; this article’s focus is the inventory status reconciliation by SKU and destination.

Treat shipment milestones, partial receipts and warehouse availability as separate records until the buyer’s receiving process reconciles them.
Keep the supplier and warehouse records connected
At PO acknowledgment, confirm that the supplier accepted the SKU, revision, quantity, destination instructions and requested dates as stated. At shipment handoff, record the relevant order lines and shipping document identifiers. At receipt, record quantity and status by destination. When a balance remains, ask the supplier or logistics contact which quantity is still open and what event supports the latest date.
If goods arrive in different cartons or lots, keep the carton labels and receipt records traceable. A buyer may need to know which revision or finish has arrived. Do not merge visibly similar products if their SKU, revision or customer destination differs. The product-specific receiving criteria remain the buyer’s responsibility.
Reconcile stale dates and exceptions before placing another order
A useful status view highlights exceptions instead of hiding them in a blended quantity. Examples include an unacknowledged PO, a supplier update older than the buyer’s policy, a shipment with no confirmed handoff, a partial receipt with an unexplained balance, a SKU mismatch, a quality hold or an estimated date that has changed. The alert rule should be the buyer’s own process; no universal number of days is prescribed here.
Assign one owner per exception. Purchasing may follow an unacknowledged PO. A supplier contact may confirm production status. Logistics may reconcile the shipment event. Warehouse operations may verify a receipt or hold. Sales operations may confirm allocations. A central planner can review the resulting picture before another order is released.
Do not overwrite the earlier status when an order changes. Preserve the previous date, new date, source and reason if known. That record helps the buyer distinguish a forecast movement from a quantity change. If the cause is unknown, say so and request clarification rather than speculating.
Supplier updates are useful but should be read precisely. “In production” can refer to an order starting, a subcomponent starting or the whole quantity moving through a step. Ask what quantity and SKU the status covers. “Ready” should have a defined meaning. A supplier’s status report should not be converted into an arrival guarantee or a claim about customs release.
The Koitor article on unconfirmed hardware POs covers the buyer’s follow-up before assuming production has started. The production-update guide covers milestone communication. Those topics support the status handoff; they do not replace the inventory planner’s own on-hand and allocation records.
Use the status view before a reorder meeting
The goal is not to let a table automatically issue a purchase order. It is to prepare a more reliable discussion. Before another order, compare physical available stock, customer commitments, open supplier quantities, confirmed shipments, destination, expected receipt and the buyer’s own demand and policy. Use the current item-location records and latest source dates.
This article does not prescribe a universal reorder formula, safety stock amount or treatment of in-transit goods in a specific accounting or ERP system. Those depend on the buyer’s data, supplier terms, lead-time history, service targets and planning method. A buyer can choose to include inbound quantities in a planning view while still keeping them distinct from physically available stock. That distinction helps avoid both double ordering and premature promises to customers.
In the meeting, present exceptions first. A SKU with plenty of physical stock and an acknowledged inbound order may require no action under the buyer’s policy. Another SKU may have a similar total but only some units available, with the rest allocated or held. A third may have a stale shipment date and an open order that needs confirmation. The view should make these cases visibly different.
A simple meeting checklist:
- Are the SKU and revision consistent across the item master, PO, supplier update and receiving record?
- How much is physically on hand at each destination?
- How much is available after buyer-defined allocations and holds?
- Which open PO lines are acknowledged and for what quantity?
- Which quantities are still in production, ready, shipped or partly received?
- What are the dates and sources for each status?
- Are partial receipts reconciled to line balances?
- Is any quantity assigned to another customer or warehouse?
- Which exceptions have an owner and next action?
- What does the buyer’s approved replenishment method say after reconciliation?
A historical system measure can help estimate demand or lead time, but it should be compared with the buyer’s actual receipts and availability. For example, NetSuite’s documentation shows that its optimization calculations use item/location settings and demand/supply inputs; that is a system-specific explanation, not an endorsement or universal replenishment rule. The buyer should check its own system’s fields and configuration before using the output to commit cash.
Treat in-transit status as an input, not as stock on a shelf
Goods that have left an origin may still face transit, destination handling or receipt processes. The buyer should record the observed milestone and status source, and keep it separate from the physical warehouse balance. The shipment’s contractual ownership, customs obligations, risk allocation and accounting treatment depend on the buyer’s actual documents and qualified professional guidance. The status view should not guess those terms.
If a shipment is delayed, identify which SKUs and quantities are affected. Ask whether the supplier has another confirmed quantity, whether an alternative shipment exists, and how the buyer’s customer commitments are affected. Do not count a new shipment and an old still-open shipment twice. Use shipment identifiers and PO line references to reconcile them.
Reconcile track in transit inventory open purchase orders by SKU
A useful inventory view does not collapse every quantity into one company-wide total. Track SKU, revision, location, condition and ownership where those attributes change the buyer’s ability to use the stock. A saleable carton in a regional warehouse is different from a sample, a damaged carton awaiting inspection, a quantity reserved for a project, or a lot held for a label correction. A part in transit may belong to a purchase order, but it is not necessarily available to promise to a customer before its expected receipt and inspection.

For each open line, retain supplier, order number, line number, confirmed quantity, balance quantity, shipment status, planned ship date, expected arrival basis, destination, and the last confirmation date. Record the source of a status update and who owns the next follow-up. A supplier’s estimated completion date, a forwarder’s booking date and a carrier tracking event describe different milestones; do not replace one with another in a dashboard. Where dates are uncertain, show a range or flag the uncertainty instead of implying precision.
Then reconcile the record against the purchase order, supplier confirmation, shipping documents and warehouse receipt. Differences should be visible as exceptions: a partial shipment, substituted revision, quantity variance, missing carton label or a receipt not yet inspected. Preserve the original ordered quantity and record the change separately so that a buyer can explain why the remaining balance moved. Avoid silently overwriting the expected quantity with what has shipped.
Software examples can help illustrate the fields, but they do not create a universal accounting policy. ERP systems vary in whether they expose in-transit, committed and available quantities in one view or require a report. The buyer’s organization should align the dashboard with its own inventory definitions and terms. Do not assume that a field named “available” means the same thing across systems.
A weekly review can focus on exceptions rather than rereading every line. Prioritize orders whose arrival could change a reorder decision, items with a promised customer date, and lines that have not been confirmed recently. Assign an owner and a next action, such as request a revised ship window, check a booking, confirm a split shipment or reconcile a receipt. The status view supports decisions; it is not a substitute for supplier confirmation or financial approval.
Buyer worksheet and FAQs
What fields belong in an open PO inventory view?
At minimum: SKU and revision; destination warehouse; physical on-hand; buyer-defined available quantity; allocations and holds; open PO lines; supplier-acknowledged quantity; production or ready status if confirmed; shipped/in-transit quantity; partial receipts; open balance; last-confirmed date; source record; exception owner. Adapt labels to the buyer’s system.
Is supplier-confirmed stock available to promise to a customer?
Not automatically. Supplier confirmation indicates an order status according to the communication or system used. The buyer should account for manufacturing, shipping, destination and receiving conditions before promising a delivery. The source and date should remain visible.
Should the buyer include in-transit goods in its reorder calculation?
That depends on the buyer’s planning method and system. Keep inbound quantities visible and separate from physical availability, and follow the company’s approved formula. This guide does not prescribe whether or how they are included.
How should the buyer treat a partial shipment?
Record the ordered, shipped, received, held or rejected, and remaining quantities by PO line and SKU. Reconcile them against shipping and receiving records, and preserve the shipment identifiers. Do not close the balance until the buyer’s process confirms it.
What if supplier and warehouse quantities do not match?
Identify the item, revision, PO line, location and date of each record. Ask the owner of the discrepancy to verify whether it is a timing difference, partial shipment, receiving delay, allocation, damage or data error. Keep the discrepancy open until the evidence supports a disposition.
Is a spreadsheet enough?
A spreadsheet can work if it has controlled definitions, source records, ownership, dated updates and change history suitable for the buyer’s needs. An ERP can still contain inconsistent inputs. Tool choice does not remove the need for reconciliation.
Does a tracking view guarantee arrival dates?
No. A view records reported or observed status. Forecast dates can change. Label estimates as estimates and preserve the source and timestamp. Do not convert them to guarantees without an agreed basis.
For a sourcing discussion, share the exact SKUs, revisions and requested order status. Koitor can clarify its own confirmed order and metal-production information within the project scope; the buyer maintains its warehouse and inventory records. Use the contact page for an order-status inquiry and identify the PO line and item.
Prepare a Clear Hardware PO Status Request
Share the SKU, drawing revision, PO line and the milestone or quantity you need confirmed. Keep supplier status separate from your own warehouse availability.
OEM / PRIVATE LABEL
Turn this sourcing guide into a product brief
Share your target product, size, finish, order quantity and packaging requirements. Your team receives a practical manufacturability review before quotation.



