Back to blog
Warehouse Operations

Best Software for Co-Packers Holding Brand Inventory

November 20, 2026

The best software for a co-packer that holds inventory for many brands is one that records an owner on every pallet, keeps each client’s lots, counts, and costs apart, and shows each brand only its own stock. A general inventory tool that tracks totals per SKU is not enough, because the hard questions in co-packing are always “whose is this?” and “where did their material go?”

This guide explains why client-owned inventory is different from your own stock, what goes wrong when the software cannot tell the two apart, and what to look for when you compare systems. It ends with an honest look at how Swift WMS handles it, including the parts that depend on your plan.

Why client-owned inventory is different

A typical manufacturer buys its materials, makes its product, and sells it. Every pallet in the building belongs to one company. A co-packer works on a different model. Brands send in their own ingredients, packaging, and labels, and pay you to make, pack, and store their product. On any given day, your warehouse might hold stock for ten brands, plus materials you bought yourself.

That means two kinds of stock share the same racks:

  • Customer-supplied materials. The brand bought them and owns them. You hold them, use them only on that brand’s orders, and report what you used.
  • Co-packer-bought materials. You bought them, often common items like a standard carton, a shrink film, or a bulk ingredient used across many formulas. You own them until you consume them and bill for them.

Your software has to know which is which, pallet by pallet. If it only knows that you have 400 cases of a carton, it cannot tell you that 300 belong to one brand and 100 are yours. That gap shows up later as a billing dispute, a wrong count in front of a client, or a recall you cannot scope.

Keep the owner on every pallet

The single most useful rule is simple: every unit of stock in the building carries an owner, from the moment it is received. In a system with license plates, that means each pallet’s record holds the customer next to the SKU, lot, quantity, and location. If you are new to plates, our guide on what a license plate number is explains how they work.

Ownership has to be set at the dock, not fixed later. The receiver should pick the customer as part of the receipt, the same way they pick the SKU and enter the lot. A pallet that enters the rack with no owner becomes a pallet that someone will guess about. Our warehouse receiving best practices cover how to build that step into the receipt so it is not skipped.

The owner then needs to travel with the stock. When a pallet is split, both halves keep the same owner. When it moves, the owner moves with it. When it is consumed into a batch, the record of what was used should still say whose material it was.

The risk of commingling

Commingling means mixing one client’s stock with another’s, or with your own, so that you can no longer tell them apart. It is the most common way co-packers lose track of client inventory, and it rarely happens on purpose. It happens when:

  • Two brands use the same supplier’s ingredient, and the receiver puts both deliveries on one pallet or one count.
  • A partial pallet of one brand’s packaging is topped up with another brand’s units to free a rack slot.
  • Staff pull from the nearest pallet of a shared SKU, not the pallet that belongs to the order’s brand.
  • Your own stock of a common item is used on a client’s order, but nobody records that it was yours.

Each of these breaks the link between the material and its owner. The fix is partly physical, such as separate pallets per owner and clear labels, and partly in software. A good system will only count a brand’s own stock, plus any stock you choose to share, as available for that brand’s work orders. Then a shortage shows up as a shortage, and nobody quietly borrows from another client.

Per-client lots and counts

Lots matter more in co-packing, because each brand has its own lot rules. One brand wants a Julian date plus a line code. Another wants its own prefix and a running number. A third prints lots on its own labels and only wants you to record them. If your software forces one company-wide format, staff end up typing lots by hand and making mistakes.

Look for a system that lets you set lot number rules per customer, so the lot printed on a finished good matches what that brand expects. The same goes for expiration date formats and label wording.

Counts need the same separation. When you count a location, you should see each owner’s plates on their own lines, not one merged total. Cycle counting by location still works, but variances must be adjusted against the right owner’s stock. Our guide to cycle counting vs. physical inventory covers how to run counts without stopping production.

Consumption reporting back to each brand

Brands want to know what happened to the material they sent you. That means a record, per batch, of which of their lots went in, how much was used, and what finished lot came out. It also means being able to show what is left.

Good consumption reporting does three jobs at once:

  • It supports billing, because materials you supplied can be charged and materials the brand supplied cannot.
  • It supports recalls, because a brand that recalls an ingredient lot needs to know which finished lots used it. Our guide on how to run a mock recall shows how to test this.
  • It supports trust, because a client who can see exactly where its material went asks fewer questions and argues fewer invoices.

If your system cannot produce a batch record that lists consumed lots by owner, you will end up rebuilding that record from production sheets every time a brand asks.

Billing for storage, receiving, and handling

Co-packers often earn money on more than production. Storage, receiving, handling, and lab testing are all services that a brand should pay for. Those charges are easy to miss when they live in a separate spreadsheet.

The software should let you bill each customer for the work done on its stock. At a minimum, look for invoice lines for storage and receiving, and a way to create storage invoices from what each customer is holding. If your system knows who owns each pallet, it has most of what it needs to bill for storing it.

Giving each brand visibility

The last piece is the one brands notice most. They want to log in and see their own inventory, their batch records and certificates of analysis, their inbound deliveries, and the status of their orders. They do not want to email you for a count every Friday.

A customer portal answers those questions without a call. The key test is scoping: each brand must see only its own stock and documents, and never another client’s. Our article on customer portals in B2B relationships goes deeper on what clients expect from one.

A buyer checklist for co-packer inventory software

Use this list when you compare systems. Ask each vendor to show it in a live demo with two test customers, not in slides.

  1. Every pallet or plate carries a customer, set at receiving and kept through splits, moves, and consumption.
  2. Your own company’s stock can be kept apart from client stock, and you can choose which of your SKUs any client’s orders may use.
  3. Stock availability for a work order counts only the right owner’s stock.
  4. Lot number rules, expiration formats, and label wording can be set per customer.
  5. Lot holds work per lot, so one brand’s held lot does not stop another brand’s work.
  6. Batch records list the consumed lots for each finished lot, and can be shared with the brand.
  7. Counts and adjustments are recorded per owner, with a reason for every change.
  8. Invoices can charge storage and receiving per customer.
  9. A customer portal shows each brand its own inventory, batch records, certificates of analysis, and inbound deliveries, and nothing else.
  10. Brands can send you their orders and inbound notices through the portal, so you are not retyping emails.

A system that does all ten will keep owners clear, lots clean, and invoices complete. A system that does only the first three is still far better than a spreadsheet.

How this works in Swift WMS

Swift WMS was built for manufacturers and co-packers that hold stock for clients, so ownership is part of the record from the start. Here is how it works today, and which plan each part needs.

Every license plate carries a customer. When staff receive stock, they choose the customer, the SKU, the quantity, the lot, and the location, and the plate’s lot is saved under that customer. A split or a move keeps the same lot, so it keeps the same owner. Plates are on every plan; see license plate inventory for the details.

For your own stock, Swift has a setting called Your Own Company. You pick the customer record that stands for your company, and SKUs owned by it can be used in bills of materials for all your customers. Stock checks for a work order count that customer’s plates plus your own company’s plates, and nothing from other clients. This covers work order availability, material requirements, schedule shortage checks, and production run staging. Work orders and bills of materials are part of Core.

Lot number rules are set per customer, on the customer’s Production tab. Each customer can have its own auto-generated format, or no rules at all, in which case staff type the lot by hand. When a lot is generated for a work order, Swift uses that work order’s customer’s rules.

For billing, WMS Invoices on Core lets you bill each customer for storage, receiving, and other work, generate storage invoices, and email them. Customers can pay online.

For visibility, the customer portal lets each brand see its own inventory, batch records with the ingredient lots that went into each batch, certificates of analysis attached to its lots, and its inbound deliveries, called ASNs in the portal. Brands can also place purchase orders through the portal. In Swift, a purchase order is the customer’s order to you, and your team approves or rejects it before work starts. The portal is included on Pro and is an add-on on Essentials and Core. Lot trace and recall impact are part of Quality on Core.

There are limits worth knowing. Swift does not create certificates of analysis; you attach the ones you receive or produce. And Swift is a browser app that needs an internet connection. To see how this fits a co-packing operation as a whole, visit the co-packers page.

The takeaway

Co-packing software is judged on one question: can it tell you, at any moment, whose stock this is, which lot it came from, and where it went? Put an owner on every pallet at the dock, keep your own stock separate from your clients’, set lot rules per brand, and give each brand a view of its own material. Do that, and billing, recalls, and client trust all get easier.

How Swift WMS does itCustomer portal