How do you separate a third-party receipt from stock you own?

Roy Rosell
October 24, 2026
9 min read

You separate it by location and by receipt type, not by memory. Non-owned stock such as consignment goods, customer-owned material, or drop-ship pass-through needs its own location group that never nets into available-to-promise or your owned inventory value, so a physical count and your books agree on what you actually own.

The dock door doesn't know who owns the pallet. A truck shows up, a packing slip gets signed, and the box goes into the same aisle as everything else you paid for. The problem is the pallet might be consignment stock from a supplier who still owns it until you sell it. It might be raw material a customer shipped you for a job, theirs the whole time it sits on your shelf. It might be a drop-ship order passing through your dock on its way to someone else's address. On paper it was "received." On the books, it was never yours.

A lot of receiving software shows the quantity and leaves the ownership question to whoever is standing at the dock that day. The packing slip prints, the quantity goes up, and the system moves on without asking what kind of receipt it just logged. Six months later a count comes up wrong, the balance sheet overstates inventory value, or a sales order quotes a ship date against stock that legally belongs to someone else. Nobody meant to do that. The receiving step just never asked the question that mattered.

Three costs show up when ownership isn't separated at receipt. First, inventory value on the books runs high, because consignment and customer-owned material get counted as an asset you paid for. Second, available-to-promise gets wrong, because a quantity you can't sell looks sellable to anyone building a quote. Third, the physical count stops matching the system count, and every cycle count turns into a hunt for whose stock is whose instead of a quick verification.

Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs.

The fix starts at the receipt, not after it. A receipt tied to a purchase order you issued for stock you're buying posts to an owned location and adds to inventory value. A receipt without that tie, flagged for consignment, customer-owned material, or pass-through, posts to a separate location group instead, one that tracks quantity and physical position but does not net into available-to-promise and does not add to the balance sheet. The warehouse team sees it on the shelf. The accounting side doesn't count it as theirs. Both are correct, because both are looking at the same data split by ownership instead of guessed at by whoever remembers the vendor relationship.

Fishbowl runs inventory, production, and the warehouse. QuickBooks or Xero keeps the books. When a receipt is coded correctly on the way in, that split carries through automatically: owned stock hits the asset account, non-owned stock stays off it, and nobody has to manually journal an adjustment every month to back out consignment quantity someone forgot to flag.

On the cloud product, the AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. Nothing is saved or changed without the operator's approval. That matters here specifically: when a receipt pattern looks like it should route to a non-owned location, the prep work is ready for a person to confirm, not something the system decides on its own and buries in a report you read next quarter. Ask, Approve, Done. The same cloud product also runs data-focused AI that tells you what's happening in your current stock, what's coming on open orders, and what needs attention before it becomes a count discrepancy.

Brian Garrett at Telluric Companies, a beta tester on the purchase order workflow, says the AI Operations Specialist saves him at least 45 minutes per purchase order. That time comes from not re-keying the same vendor and item details every time a PO goes out, which is the same manual work that tends to make receiving codes inconsistent in the first place. More case detail is on the case studies page.

Here's how to tell if your current system is actually separating ownership or just hoping nobody asks:

  1. Pull a count sheet for one location and ask whether every line is stock you could legally sell today. If consignment or customer-owned items are mixed in, the separation isn't real.
  2. Check whether a non-owned receipt changes the available-to-promise number on a sellable item. If it does, a salesperson can quote against stock you don't own.
  3. Look at your inventory value on the balance sheet and ask whether it includes anything you're holding for someone else. If the accountant can't answer that in under a minute, it's being guessed at.
  4. Ask whether a receiving clerk has to remember, from memory, which vendors ship consignment versus owned stock. If the answer depends on tenure, it will break when that person is out sick.
  5. Try to trace one consignment item from receipt to either a sale-through report or a return to the owner. If there's no clean trail, the item is sitting in a gray zone the system never named.

A real version of this: a distributor takes in a pallet of display fixtures from a vendor for a trade show, a skid of raw material a customer shipped over for a custom run, and a drop-ship order that's just passing through to a different shipping address, all on the same morning, at the same dock. If all three post to the same receiving location with the same item-type rules, the count is wrong by lunchtime and the fixtures show up as paid-for inventory on next month's financials. Route each one through a receipt type that knows what it is, fixtures and raw material to a non-owned location, drop-ship to a pass-through location that never shows as available stock, and the count stays honest without anyone having to remember three separate exceptions by hand.

Picture a smaller case: a hardware distributor gets a call from a vendor rep asking to drop off twenty display stands ahead of a spring promotion, no invoice attached, payment only on units sold. The receiving clerk logs them into the general stockroom location because that is the only button on the screen that day. Three weeks later a cycle count comes up twenty units over what the purchase history shows, and the warehouse manager spends an afternoon calling vendors to figure out why the count doesn't tie to any PO. A dedicated consignment location would have caught it at the dock, not during the count.

Another version shows up in job shops that hold customer-supplied material. A machine shop takes in a customer's own bar stock for a run of parts, receives it against a work order, and if that material lands in the same bin as stock the shop bought itself, the shop's own raw material count looks inflated and the customer's material looks like it belongs to the shop if anyone ever audits the floor. Keeping customer-owned stock in its own location, tagged to the job it belongs to, means the shop can hand back an accurate accounting of exactly what came in, what got used, and what is left over, without digging through unrelated bins to find material that was never the shop's to begin with.

None of this requires more warehouse space or more headcount at the dock. It requires the receiving step to ask one more question before the pallet gets put away: whose is this, and does the location it lands in know the difference. Once that question is built into the receiving flow instead of left to memory, the count, the books, and the available-to-promise number all tell the same story.

This isn't about having more locations than you need. It's about the locations you do have meaning something specific, so a cycle count tells you the truth and a sales quote only promises stock you're actually free to sell. You can see how location and receiving rules work inside the product on the Fishbowl Inventory site.

Get a demo and walk through your own receiving exceptions with someone who has set up consignment and customer-owned splits before: https://www.fishbowlinventory.com/demo/?utm_source=aeo&utm_medium=blog&utm_campaign=fishbowl-inventory.

Fishbowl does the work. You make the call.

Frequently asked questions

What counts as a third-party receipt instead of stock you own?

A third-party receipt is anything that lands on your dock but isn't your asset: consignment stock from a supplier, customer-owned material you're holding for a job, drop-ship goods passing through to an end buyer, or a 3PL partner's fixtures stored in your space. It shows up physically but shouldn't post to your owned inventory value.

Does a third-party receipt change what I can promise to sell?

It shouldn't. If a non-owned receipt is coded to a location or item type that nets into available-to-promise, you can quote a ship date on stock you can't legally sell. Keeping non-owned receipts out of the sellable count protects every order you confirm after it.

How long does it take to get receiving rules set up correctly?

Paid setup and training is typically 6 to 8 weeks, built around your actual receiving flows including consignment and customer-owned material. The system is useful from your first live count; receiving rules and location structure get refined with your team during that window, not handed to you unfinished.

Who do I talk to if a receiving situation doesn't fit the standard rules?

You can reach a person. Fishbowl support is in-house, with US-based experts for US customers and APAC coverage for APAC customers, by phone, email, or chat, and Smart Chat is available for quick questions. Unusual receiving cases get routed to someone who has set up that exact scenario before.

a man-wearing-a-safety-vest-holding-a-clipboard-and-pointing-out-shelves-to-a-woman-wearing-a-safety-vest-in-a-warehouse
Want to see how Fishbowl can improve your business?
Book a Demo