Wholesale Pack Size Management: Cases, Cartons and Each

Wholesale pack size management means keeping the relationship between individual units, sales packs and supplier cartons explicit from order entry to delivery and invoicing. Choose a consistent stock unit, record each permitted conversion and make the unit visible beside every quantity and price. A number such as “10” is not enough when one person means ten cases and another means ten items.

The problem often begins with an ordinary customer email. Sales enters five boxes, purchasing uses the supplier’s carton size, and the warehouse sees a quantity without the conversion. Each team can follow its own instructions and still produce the wrong result.

A dependable wholesale order management system carries the unit, pack definition and resulting stock demand through those handoffs. You may be able to achieve this by configuring your existing software. Integration or a custom workflow becomes relevant when the same ambiguity keeps returning.

This guide explains what to record, how to handle partial packs and changing supplier sizes, and which checks to include before buying or changing software.

Illustrative stock-storage photograph: a carton is a physical container, while its recorded contents determine the quantity available to sell. This is not an OpsMavix client site.

Image credit: FIONASUN, via Wikimedia Commons, CC0 1.0. Displayed at a reduced size; no additional edits.

Key Takeaways

• Record the unit with the quantity and price. Five cases and five individual items are different demands.
• Define a base stock unit and product-specific pack sizes; do not assume every supplier’s “box” contains the same number.
• Keep a sales pack, a shipping container and an assembled kit distinct. Their stock behaviour can differ.
• Preserve the conversion used on historical orders when a supplier changes its carton size.
• Test broken packs, shortages, returns, customer pricing and duplicate imports as one complete workflow.
• Compare configuration, integration and custom development against demonstrated errors and measurable administration.

In this guide:

• 1. Choose the Stock Unit and Name Every Pack
• 2. Separate Pack Sizes From Packages and Kits
• 3. Carry Quantities and Prices Through Order Entry
• 4. Reserve and Pick the Actual Units Required
• 5. Receive Supplier Cartons Without Rewriting History
• 6. Handle Broken Packs, Short Deliveries and Returns
• 7. Compare Configuration, Integration and Custom Software
• 8. Pilot the Rules and Measure the Remaining Work
• Frequently Asked Questions
• How OpsMavix Can Help

1. Choose the Stock Unit and Name Every Pack

Start with the item you can reconcile

For a countable product, the base stock unit might be one item. For another product, it could be a metre or kilogram. Choose a unit that represents the material you actually control and can reconcile at receipt, issue and count.

Then define the sales and purchasing units that relate to it. A case of twelve items and a supplier carton of twenty-four can both refer to the same product without creating independent stock balances.

Hypothetical product record:

Avoid generic conversion rules

“Box” is a description, not a universal conversion. Product A100’s box may contain twelve items while B200’s contains ten. The conversion needs the product and the defined packaging reference.

Likewise, do not convert weight to count or volume using an assumed universal factor. Those relationships require appropriate product information and a process for actual measurement where relevant.

Show both quantities where useful

The order desk might see “5 cases of 12 = 60 each”. The warehouse should see the same demand expressed in the units used to pick.

The conversion should be calculated once from the approved definition. Asking three teams to calculate it independently creates three opportunities for disagreement.

2. Separate Pack Sizes From Packages and Kits

Similar labels can describe different records

A pack size tells you how many units a commercial pack contains. A package can identify a physical carton or pallet. A kit groups components into something sold together. Decide what each record means before designing its stock effect.

Use existing capabilities fairly

Odoo’s units-of-measure documentation describes conversions between purchasing and sales/inventory units. Its packaging guidance distinguishes units, packages and packaging records. The latter is an older version, so confirm behaviour in your installed release.

These are reasons to inspect configuration before assuming a custom build is required. A platform feature still needs correct product definitions and an end-to-end demonstration.

Give mixed cases their own treatment

An assortment of six flavours is not simply “six each” of one item. Define the component mix, whether substitutions are allowed and whether assembly changes stock.

The same principle applies to kitting. A label on a sales line must connect to the actual components required, including any separately controlled packaging material.

3. Carry Quantities and Prices Through Order Entry

Make the commercial agreement unambiguous

An order line needs product identity, ordered quantity, ordered unit, conversion, price basis and the resulting amount. A price of £30 means something different per case than per individual item.

Hypothetical example: a customer orders five cases of twelve, priced at £30 per case.

These figures exclude tax and delivery charges. They illustrate unit consistency, not a recommended pricing policy.

Keep customer references mapped

A customer may use its own item code or describe the product by an older pack name. Store the mapping to the approved internal product and pack definition.

An ambiguous email should become an exception for review. If an automated reader extracts “5 boxes”, it should not silently choose a pack size without the information needed to identify it.

Check imports at the boundary

For a portal, EDI message or marketplace connection, establish whether the quantity is already in base units. Applying a conversion twice can multiply demand by the pack size again.

Retain the original reference and interpreted unit alongside the internal record. When an order is replayed after a timeout, its identity should prevent a duplicate commitment.

4. Reserve and Pick the Actual Units Required

Separate physical stock from availability

On-hand stock includes goods physically recorded at a location. Availability also depends on reservations, holds and your commitment rules.

If A100 has 72 eligible items and another order already reserves 24, only 48 remain free under a simple on-hand-minus-reservations rule. A new five-case demand of 60 items cannot be fully covered from that free stock.

Do not promise from the number of cartons visible on a shelf without accounting for their recorded contents and existing commitments. This is part of inventory control, even when customers buy in packs.

Respect physical presentation

Sixty items may exist as five sealed cases, several broken cases or loose items in different bins. If the customer requires sealed cases, a base-unit total alone does not prove fulfilment readiness.

Decide whether sealed-pack status needs its own record. The requirement should follow the product and customer agreement, rather than be assumed for every item.

Make picking instructions actionable

A picker should be able to identify the product, location, quantity and handling unit. Where barcodes represent a whole pack, scanning one pack should apply its approved quantity rather than always one item.

Test the actual labels and devices. A correct conversion in the product master is not enough if the scan screen displays an ambiguous quantity or lets the wrong packaging barcode pass unchecked.

5. Receive Supplier Cartons Without Rewriting History

Record what arrived

Receiving should capture the supplier item reference, observed pack definition, accepted quantity and any difference from the purchase order.

Hypothetical receipt: four cartons of twenty-four arrive. Three are complete; the fourth contains twenty items. Accepted stock is (3 × 24) + 20 = 92 each, not 96.

Keep the shortage visible for the purchasing team. A receipt record should not be increased to match the invoice simply because the supplier billed four full cartons.

Illustrative warehouse photograph: receipt and picking records need to distinguish carton quantities from the units inside them. This is not an OpsMavix client site.

Image credit: Nenad Stojković / Shixart1985, via Wikimedia Commons, CC BY 2.0. Displayed at a reduced size; no additional edits.

Version a changed pack definition

Suppose the supplier changes its carton from twenty-four items to twenty. Record the effective change and review outstanding orders.

A historical purchase for four cartons of twenty-four should continue to explain 96 expected items. Editing today’s product default must not reinterpret that old transaction as 80.

Store the conversion on the transaction or retain an appropriate version reference. Decide how existing reservations, supplier messages and barcode mappings are reviewed when the definition changes.

Keep invoice matching consistent

Purchasing, receiving and accounting may display different units while still describing the same goods. Matching requires an agreed conversion and price basis.

The supplier’s invoice quantity should reconcile to what was ordered and accepted, with short or damaged receipts handled as exceptions. It should not force the warehouse into maintaining a second editable stock balance.

6. Handle Broken Packs, Short Deliveries and Returns

Define the permitted exception

If the normal sales unit is a case of twelve, decide whether a customer can buy eighteen items. The system needs to distinguish a permitted broken-pack sale from an entry error.

Preserve the original order and the actual outcome

For a partial delivery, record ordered, delivered, outstanding and cancelled quantities in a consistent unit, with the customer-facing unit shown alongside.

If four cases ship from a five-case order, the remaining demand is one case or twelve items. Do not overwrite the order to four cases and lose the evidence of what was originally agreed.

Treat returned quantity and credit separately

A commercial credit may be expressed per case while only some physical items return. Record the actual receipt and approved condition separately from the financial adjustment.

Returned stock should become sellable only after the required review. The workflow for food, controlled goods or damaged products may require additional checks; unit conversion does not replace them.

7. Compare Configuration, Integration and Custom Software

Demonstrate the same scenario in every option

Use your own product, supplier carton, customer pack, price and return scenario. Include one changed pack size and one duplicate import.

Measure the current administration

Count the corrections caused by pack ambiguity, the time spent resolving them and any documented cost. Separate genuine unit mistakes from unrelated stock discrepancies.

Hypothetical capacity example: twenty corrections a week taking six minutes each equal two staff hours. At an illustrative £30 per hour over 48 weeks, that is £2,880 of annual staff time. It is not automatically a cash saving, and it does not by itself justify a large project.

Include the cost of maintaining definitions

The team still needs to approve supplier changes, resolve unclear orders and review new products. Software can make these tasks visible and consistent; it cannot decide an unknown carton size from nothing.

Include migration, configuration, training, integration support and remaining manual review when comparing proposals. A low subscription price is only one component of the operating cost.

8. Pilot the Rules and Measure the Remaining Work

Choose a small but revealing sample

Use one product sold in full cases, one sold as loose items and one with a supplier-specific carton. Add a kit if your business sells them.

Reconcile current stock in base units, including broken packs and held goods. Confirm outstanding orders before importing a new opening balance.

Set acceptance checks before launch

The pilot should prove that:

• The same order retains its meaning from entry to invoice.
• Customer and supplier codes map to the intended product and pack.
• Reservations use the correct base quantity.
• Scanning a pack applies the approved number of units.
• Short receipts record actual accepted contents.
• A new supplier pack definition leaves historical transactions understandable.
• Partial deliveries and returns preserve quantities and status.
• Duplicate messages do not duplicate orders or movements.
• Exports include the unit and conversion needed for handover.

Review exceptions before expanding

Track ambiguous lines, conversion corrections and unresolved shortages. Compare the results with the original baseline and investigate the remaining causes.

Expand after the team can explain the records and maintain the definitions. The goal is fewer avoidable misunderstandings across the order desk, warehouse and accounts, with clear responsibility for the exceptions that remain.

Frequently Asked Questions

What is wholesale pack size management?

It is the controlled relationship between individual stock units, sales packs and supplier cartons. Quantities, prices and transactions retain their unit and conversion throughout the workflow.

Should we hold stock in cases or individual items?

Choose a unit that you can reconcile and that supports actual handling. Countable goods are often controlled in each, with pack equivalents displayed. Sealed-case requirements may need additional presentation or status records.

Is packaging the same as a unit of measure?

Not necessarily. A unit measures quantity; a packaging definition describes a product pack; a physical package identifies a container. Check how your software represents each and how it affects stock.

Can our current ERP already handle different purchase and sales units?

It may. Test its configuration with your real product and transaction flow. Published conversion features are a reason to investigate existing capabilities, not proof every customer and supplier exception is covered.

How do we prevent a pack conversion being applied twice?

Define the unit at each integration boundary and record whether the incoming quantity has already been converted. Test a known case quantity and a replayed message against the resulting stock demand.

What happens when a supplier changes carton size?

Update the approved definition and review outstanding work. Preserve the conversion used on historical transactions so previous orders and receipts remain explainable.

Can we sell part of a case?

If your product and customer rules permit it. Configure permitted quantities, prices and picking instructions explicitly. Do not let an accidental fractional case become a silent exception.

Should a credit note automatically put a whole case back into stock?

No assumption like that should be built into the workflow. Record what physically returns, its condition and the approved disposition separately from the commercial credit.

When is custom software justified?

When a demonstrated, valuable gap remains after testing configuration and integration, and the project cost and ongoing support fit the problem. The scope may be a focused handoff or a wider ERP where shared controls are needed.

How OpsMavix Can Help

OpsMavix builds wholesale order management systems around the way customers order, suppliers deliver and warehouses fulfil.

We can help map product and pack definitions, customer references, purchasing units, price bases, reservations, partial deliveries and returns. We assess the capabilities of your current tools before recommending configuration, integration or a custom build.

Where the problem extends across departments, OpsMavix can build a broader ERP with shared records. Where the gap is narrower, a focused workflow can connect the tools you already use.

Bring one order where “box”, “case” and “each” produced different answers, together with the purchase, receipt and invoice records. Book an Operations Leak Audit and we will identify the missing rule and a practical way to test the fix.