When purchasing buys cartons but stores count pieces

A storekeeper receives five cartons. Purchasing sees five cartons on the order. The stock screen shows five units. Everyone entered the number correctly, but the business still does not know how many bottles arrived.

Before automating purchasing or adding an AI assistant to inventory, settle what one unit means at every step. The receiving screen should make the conversion visible while somebody can still check the delivery.

Follow one item from order to issue

Consider a hypothetical hotel buying cleaning solution. This is a worked example, not a client result. The supplier sells a carton of 12 one-litre bottles. Stores counts bottles, and housekeeping receives bottles.

An order for five cartons represents 60 bottles. If only four cartons arrive, the receipt should show both four cartons received and 48 bottles added to stock, with one carton still outstanding. If housekeeping takes seven bottles, the remaining stock from that receipt is 41 bottles, assuming no other movements.

Those numbers describe different stages. An ordered quantity should not become available stock merely because the purchase order was approved. Likewise, an invoice for five cartons does not prove that all five arrived. Keep the order, receipt, issue and supplier invoice connected, with their own quantities and statuses.

This is more specific than a general invoice matching exception queue: the documents may appear to disagree because their quantities use different units. Establish the conversion before deciding whether a mismatch is real.

Write the conversion rule where the team can inspect it

For each item, agree a stock unit and the purchase packs it can arrive in. A useful item record contains:

• The internal item identifier and supplier item reference.
• The stock unit, such as bottle, kilogram or metre.
• The purchase pack identifier and its description.
• The approved conversion, such as one carton of this pack equals 12 bottles.
• The source used to verify the pack, the person who approved it and when it became valid.
• Whether fractional quantities are allowed and how rounding is handled.

“Carton” on its own is not a conversion. Another supplier may put ten bottles in a carton. Even the same supplier may sell two pack sizes. Tie the rule to the specific item and pack rather than maintaining one universal carton multiplier.

Store the original quantity, original unit, conversion used and resulting stock quantity on the transaction. A later edit to the item record should not rewrite the meaning of a delivery accepted last month.

Treat a changed pack as a decision

Suppose the next delivery contains cartons of ten bottles, while the open order still expects cartons of 12. Receiving five cartons now gives 50 bottles, not 60.

The system should surface the difference before the receipt posts. The receiving owner checks the packaging and supplier paperwork; purchasing decides how to handle the outstanding order and price basis. The record should show whether the team accepted a substitution, expects more goods or needs a corrected document.

Do not quietly change the master conversion to ten and apply it everywhere. That could make an old four-carton receipt appear to contain 40 bottles instead of the 48 actually received. Returns also need the original receipt context: returning one unopened old carton removes 12 bottles, even if new deliveries use packs of ten.

Where both packs remain in stores, make them distinguishable in the receiving and picking process. Depending on the operation, that may require separate pack identifiers, labels or lot records. A dropdown that says only “carton” leaves the ambiguity with the person at the shelf.

Give AI the reading task, with a review boundary

An AI extraction step can propose that “4 ctn x 12 btls” means four cartons containing 12 bottles each. Show the source description alongside the proposed item and pack so the reviewer can check it.

The posting rule should then use an approved conversion. If the document says only “4 boxes,” the workflow needs clarification. A confident interpretation of the word “box” is not evidence of its contents.

Keep two other boundaries explicit. Bottles and litres are different measures: a one-litre bottle is not interchangeable with a 750-millilitre bottle. And a fixed conversion from pieces to kilograms is unsuitable when actual weight varies. In those cases, capture the measured quantity the operation needs instead of forcing every receipt through one multiplier.

The same approval rules used for AI copilot record changes apply here. Reading a document, proposing a mapping and changing stock are separate permissions.

Test the awkward deliveries before rollout

Ask purchasing and stores to walk through these cases together in a test environment:

1. Normal receipt: five cartons of 12 add 60 bottles and retain the purchase-unit view.
2. Partial receipt: four cartons add 48 bottles; the remaining order stays visible without adding stock prematurely.
3. Loose delivery: two cartons plus three loose bottles add 27 bottles, using an explicit entry method the receiver understands.
4. Changed pack: a carton of ten against an order for packs of 12 pauses for a recorded decision.
5. Return: a return against the old receipt uses its original pack definition.
6. Correction: a mistaken receipt is corrected through a traceable reversal or adjustment, with dependent movements checked.
7. Unknown unit: an unmapped “box” cannot post a guessed stock quantity.

For each case, inspect the stock movement as well as the form. Confirm the source document, unit labels, remaining order quantity and resulting balance. If the proposed solution handles the normal case but needs an unexplained spreadsheet for returns, the workflow is still incomplete.

Measure whether the fix removes work

Start with a sample of recent receiving discrepancies. Separate unit errors from shortages, damaged goods, wrong items and entry mistakes. Otherwise, a general stock-variance number can hide whether the pack rule helped.

After the change, track unit-related corrections, time spent checking ambiguous receipts and unresolved pack exceptions. Include the effort needed to maintain pack definitions. Use those observations in the automation ROI review; do not count every stock discrepancy as a saving from this one fix.

Before commissioning a new system, demonstrate these cases in the ERP you already use. Existing configuration may cover them. Where it cannot, scope the missing receiving or integration behaviour around the actual rule.

For a workflow review with SolvTree, bring one purchase order, its receipt, a stock issue and a return for the same item, with sensitive details removed. That small chain is enough to start locating where the unit changes meaning.