Article

Receiving client inventory: ASNs, discrepancies and lots

Receiving is where a 3PL's numbers start. If a client sends 480 units and your dock books 500, every stock report, every order and every storage charge after that is built on a number that was never true. And when the client asks why their count is short, the only evidence is whatever someone wrote on the delivery note.

OpenBoxes Lift receives against an advance shipping notice and records every difference from it. This article covers the ASN, receiving on the dock, how discrepancies are recorded and settled, and how lots and expiry dates are handled. The SKUs, lots and quantities are invented examples.

The ASN: what is coming#

An ASN (advance shipping notice) tells your dock what is arriving for a client: which SKUs, how many, and, for lot-controlled products, which lots and expiry dates. In Lift, ASNs live under Inbound in the portal sidebar.

There are three ways to create one:

  • The form. Choose New ASN, pick the client, and give it a reference. Add the expected arrival, supplier, carrier and freight reference if you have them, then a line for each SKU with its quantity, and its lot and expiry where they are known.
  • A CSV upload. One row per line, with rows sharing an asn_reference making one ASN. Every ASN from a file starts as a draft, so you can check it before submitting.
  • The API. ASNs can come straight from your own systems or your clients', and an ASN can be looked up later by its reference.

When an ASN is submitted, Lift sends it to OpenBoxes as an inbound movement into that client's depot. It then shows In transit, ready for your dock.

A good habit to set with each client from the start: no ASN, no appointment. A delivery with a notice behind it is quick to receive and easy to check. A delivery without one is a puzzle.

Receiving at the dock#

Receiving happens in OpenBoxes, against the inbound movement Lift created. Your team can do it at the desktop or on the handheld.

The receiving sheet. Open the ASN in the portal and choose Receiving sheet for a printable sheet. It lists each line's SKU, lot, expiry and expected quantity, with a column to write the count in and a sign-off for who received it and when. Count damaged or expired units apart and tell the office.

On the handheld. Open Receive and scan the shipment number, or choose it from the list. For each line, scan the product, scan or type the lot, enter the expiry date from the label, scan the bin you are putting it in, type the quantity, and save the line. When every line is in, complete the receipt.

Either way, the count comes from what is physically there, not from the ASN.

Discrepancies: what did not match#

Once stock is received, Lift compares it with the ASN and records each difference on the ASN's page:

  • Fewer units than expected, or more units than expected.
  • Received under another lot, or received with another expiry date.
  • Expired on arrival.
  • Product not on this ASN.

Each discrepancy stays Open until it is settled. It is either Confirmed, when you close the ASN accepting it as recorded, or Cleared, because a later receipt resolved it. For example, a later receipt that makes up a short line clears it.

Damaged and expired units#

Some units arrive and should not go into stock. Choose Record damage on the ASN to enter, for each line, the units that arrived damaged or expired and were not received. The ASN then shows why the received count is lower than the notice.

Closing the ASN#

When everything is settled, choose Close ASN and pick a reason:

  • Discrepancies confirmed as recorded
  • Short shipped by the supplier
  • Damaged or expired units
  • Inbound can no longer be followed in OpenBoxes
  • Other reason

A received ASN with nothing left open closes on its own about two hours after the receipt. Only the ones that need a decision wait for you.

The delivery nobody announced#

Sometimes a pallet arrives that matches no notice. Choose Unplanned delivery on the ASN it arrived with, and Lift creates a new ASN linked to it. The stock is still received against a record.

Lots and expiry dates#

For products that are lot controlled, each ASN line can carry its lot and expiry date. A lot is up to 64 characters, and an expiry date needs a lot.

Two things to agree with clients early:

  • Send the lot exactly as printed. A2417 and A-2417 are two different lots. If the client's system writes lots one way and the manufacturer's label another, decide which one wins before the first delivery.
  • Split mixed deliveries by lot. If a carton of 500 holds two lots, that is two lines on the ASN, for example 300 of A2417 and 200 of A2502.

When the dock receives a different lot or expiry date from the one on the ASN, Lift records it as a discrepancy rather than quietly accepting it. That is often the first sign of a labelling problem at the supplier, and it is far easier to sort out on the day than at the next recall.

Whether a product is lot controlled is set when it is first imported, and it cannot be changed afterwards. Decide it per product before the first import.

The receiving report#

Inbound, Receiving report downloads a CSV of received lines for a client and a date range. It has the expected, received and damaged quantities, the lots and expiry dates, the close reason, the discrepancies, and the minutes from arrival to stock for each ASN. It is the document to send a client who asks what arrived last month, and a quick way to see how long stock sits at your dock before it is put away.

Where receiving meets billing#

Receipts, receipt lines, units received, damaged units and unplanned receipts can each be charged on a client's rate card. Lift counts them from the same receipts, so the receiving charges on the monthly invoice match the receiving report. Client Billing covers the invoice.

Read more#

Receiving and ASNs in the docs has every field, status and API call. The 3PL page has an overview of Lift for 3PLs, and the pricing page has the 3PL plans.

Want a 30-minute setup call? Ask in the support chat and we'll set a time.

Keep reading