Customer Pickup (Will-Call): Identity, Staging and Release

A driver walks up to the will-call window at 13:40 and says he is collecting for Rao Builders. The clerk types the customer name, finds two pallets in lane WC-08, takes a signature on a paper ticket and waves the truck out. At 16:20 the real Rao Builders driver arrives for those pallets. The first driver had been sent for a different Rao order, three pallets sitting one lane over, which are still there.

Nobody lied and nobody stole anything, yet the counter has two unhappy customers, one pallet set to recover and an invoice that no longer matches what left. Will-call failures are almost always matching failures: the wrong person matched to the right order, or the right person matched to the wrong pallets. A counter that binds identity to authority, keeps every held order in a known location, and scans each unit at the door can keep mis-releases near zero.

• What this guide covers: pickup types and their legal consequences, authorised collector lists and pickup codes, staging and ageing, the release scan, US and Indian paperwork, and counter economics.
• What it adds: a timestamped mis-release trace, a release-event payload, a worked cost model in USD and INR, and a 30-day opening checklist.

Three kinds of pickup and the paperwork each one triggers

Every will-call release is one of three events, and each produces different documents and a different moment when risk moves. Decide which one is happening before the clerk prints anything, because the counter procedure branches on it.

• Buyer's own vehicle: the customer's employee collects in a company van or truck. No carrier is involved, and in the US risk of loss usually passes when the buyer receives the goods.
• Carrier sent by the buyer: a trucking company arrives under the buyer's routing instructions. That is a tender to a carrier, so a bill of lading or receipt is issued and carrier liability rules start to apply.
• Agent or courier: a third person collects on the buyer's behalf with written authority. Treat the authority letter as part of the order, not as a document the driver happens to carry.

The legal anchors differ by market. In the US, UCC 2-509(3) says that where the seller is a merchant, risk passes to the buyer on receipt of the goods, unless a contract says otherwise. When goods sit in a third-party warehouse, 2-509(2) applies instead, and risk can turn on the warehouse acknowledging the buyer's right to possession. A carrier pickup falls under 49 U.S.C. 14706, which requires the carrier to issue a receipt or bill of lading for property it receives.

Will-call release in a US distribution centre moves risk of loss to the buyer on receipt under UCC 2-509(3) when the seller is a merchant, so the warehouse release record, signed by a listed collector and timestamped to the second, decides ownership of any pallet damaged after the 14:05 signature.

In India the GST documents decide whether the goods may move at all. Section 31(1)(a) of the CGST Act requires the tax invoice before or at the time the goods are removed for supply. CGST Rule 138(2) covers the case where the recipient transports goods as consignee in its own or a hired conveyance, and the e-way bill then needs Part B with that vehicle's number.

Authorised collector lists and a one-time pickup code

Photo ID proves a person's identity, not their right to take your customer's goods. Authority has to come from the buyer before the collector arrives, through a list of named collectors held on the customer account and a one-time code sent to the buyer's contact when the order is staged.

The authorised list belongs on the customer master, maintained by customer service and confirmed by the buyer in writing at least once a year. Each entry carries a name, the collecting company and an expiry date. When the order is staged, the warehouse system sends a six-digit pickup code to the buyer's registered contact, who passes it to whoever they send. The collector then needs both the code and a name on the list.

• Record, do not copy: note the ID type and its last four characters on the release record, instead of photocopying or scanning the whole card, so the counter holds the minimum personal data.
• Code per order: issue one code per order, not per customer, so a collector sent for one order cannot take another staged for the same account.
• Unlisted collector: if the name is not on the list, the clerk calls the buyer's registered number, never a number the collector offers, and records the call time and the person who approved.
• Code expiry: expire the code when the order is released or returned to stock, so an old message cannot unlock a new order.

Staging lanes, will-call locations and the age limit on held orders

A held order must sit in a system location that belongs to it alone, never on "the floor by the counter". Create a will-call location type in the warehouse management system, one location per staged order, with a clock that starts at staging and an action that fires when the order ages past its limit.

Each staged unit carries a label with the order number, the unit count (for example 2 of 3), the staging time and the location code. The location code should match the lane signage, such as WC-07, so that a clerk walking to the lane can confirm the location before scanning. Orders with more than one unit occupy one location; splitting an order across two lanes is how partial releases start.

Will-call staging in a warehouse management system works when each held order occupies one dedicated WC location with an age clock; a 5-business-day collection limit, followed by a recorded return-to-stock or storage-charge decision, keeps staged stock below a target of 2% of forward pick locations.

Ageing is a commercial decision as much as an operational one. At day 3 customer service reminds the buyer; at day 5 the will-call lead either reschedules the pickup with a storage charge agreed in the terms of sale, or cancels the order and moves stock back to its pick face. Indian sites have an extra reason to watch the clock, because Rule 138 keeps a Part A e-way bill number open for 15 days for Part B to be added.

The release scan: every handling unit checked against the order

The release scan is the last point where a wrong pallet can be stopped, so it must block rather than warn. The clerk scans the will-call location, then every handling unit; the system refuses any unit not on the order and refuses to close the release until the count matches or a supervisor records a short.

The release event below is what the warehouse system writes when the scan completes. It stores the evidence a dispute will need, links the collector to the authority check and records the vehicle number that the Indian e-way bill requires. The structure is an example to adapt, not a published standard.

{
  "release_id": "WCR-2026-11-000431",
  "order": "SO-118204",
  "location": "WC-07",
  "staged_at": "2026-11-12T09:12:00+05:30",
  "collector": {
    "name": "Suresh Patil",
    "company": "Rao Builders",
    "on_authorised_list": true,
    "pickup_code_valid": true,
    "id_type": "DL",
    "id_last4": "4471"
  },
  "vehicle_number": "MH04AB1234",
  "units_expected": ["HU-0003012", "HU-0003013", "HU-0003014"],
  "units_scanned":  ["HU-0003012", "HU-0003013", "HU-0003014"],
  "rule": "release only if units_scanned == units_expected",
  "documents": { "invoice": "INV-26-08817", "eway_bill": "EWB-PART-B-UPDATED" },
  "signed_at": "2026-11-12T14:05:31+05:30",
  "clerk": "counter-2"
}

Two exceptions need written rules. A short release, where the collector takes two of three units because the vehicle is full, needs a supervisor approval and a new release for the remainder. A substituted vehicle, where a different truck arrives than the buyer announced, is acceptable for a US own-vehicle pickup but in India changes the Part B entry, so the clerk updates it before the goods move.

A mis-release traced through the counter log

The trace below rebuilds the opening example from the counter log. Each step was a reasonable action by a busy clerk; the failure came from searching by customer name instead of scanning the location and units against a code-bound order.

1. 09:12, staging: order SO-118204 (three pallets, HU-0003012 to HU-0003014) is staged in WC-07. Order SO-118240 for the same customer, two pallets, already sits in WC-08.
2. 13:40, arrival: the collector says "pickup for Rao Builders". No pickup code exists in the old process. The clerk searches by customer name, and the first result is SO-118240.
3. 13:44, release: the clerk walks to WC-08, takes the two pallets, gets a signature on a paper ticket and posts goods issue by hand, without a unit scan.
4. 16:20, second arrival: the collector sent for SO-118240 finds WC-08 empty. The counter now owes one customer two pallets and has an invoice for SO-118240 that the wrong person signed.
5. Controlled run, 13:41: with codes and scans, the collector's code opens SO-118204 only. Scanning WC-08 returns "location not on order", and the clerk goes to WC-07 instead. Total delay: under two minutes.

Which counter checks are system rules and which stay with the clerk

Matching rules belong in the warehouse system; judgement about people and documents stays with the clerk and supervisor. Software can read and suggest, for instance by pre-filling a name from an ID card photo, but the decision to release rests on rules that cannot be overridden without a named approver.

The checks for electronic signatures and the evidence a court or claims desk expects are covered in our guide to whether an electronic proof of delivery is legally valid. The same retention and attribution points apply to a will-call signature captured on a counter tablet.

Invoices, e-way bills and revenue at the moment of collection

In India the invoice and, above ₹50,000, the e-way bill must exist before the goods cross the counter; in the US the release record mainly settles risk and revenue timing. Build the counter so that documents print as part of the release, not after it.

The Indian sequence works best in two steps. Raise the invoice and Part A of the e-way bill when the order is staged, using the delivery address and value. When the collector arrives, read the vehicle number from the truck, add Part B, and only then complete the release. Rule 138A requires the person in charge of the conveyance to carry the invoice and the e-way bill copy or number, so the collector leaves with both.

Will-call dispatch in India requires the tax invoice before or at removal under CGST Section 31(1)(a) and, for consignments above ₹50,000, an e-way bill whose Part B carries the collecting vehicle's number under CGST Rule 138(2); the counter should block release until both numbers appear on the gate pass.

If a collector does not turn up after Part B is added, Rule 138(9) allows the e-way bill to be cancelled within 24 hours of generation, provided it has not been verified in transit. For how the invoice and e-way bill relate when e-invoicing applies, see the guide to e-invoice IRN and e-way bill generation.

In the US, the timestamp on the release record usually marks when control passes for an own-vehicle pickup, which affects period-end revenue and inventory. The guide to shipping terms and revenue recognition covers that accounting in detail. The operational rule is simpler: no release record, no goods issue, so the ledger and the dock always agree.

Counter economics: a worked example in dollars and rupees

Release scans and pickup codes pay for themselves through avoided mis-releases, not through faster counters. The worked example compares a US distribution centre and an Indian one, each with two counter clerks, before and after the controls. All figures are illustrative.

The cost of one mis-release is built from parts a manager can check. In the US: a $180 recovery run, 1.5 hours of re-pick and re-stage at $31, and 2 hours of credit and dispute work at $38. In India: a ₹2,800 return trip, 1.5 hours at ₹250 and 2 hours at ₹400, which also covers cancelling and re-issuing the e-way bill.

Opening or fixing a will-call counter in 30 days

A counter can move from name searches to code-bound releases in about a month if master data, locations and scan rules are set up in that order. The checklist below lists each step, its owner and the test that proves it works.

Retail curbside pickup raises different questions, such as order-ready messaging and parking-bay handover; the curbside and micro-fulfillment buyer guide covers that software evaluation, while this article stays with B2B collections at a warehouse counter. More operating guides are on the logistics and supply chain hub, and if you are specifying a warehouse system that must enforce these rules, you can describe your counter through our request for proposal form.