Written by DROPS.ST.
A head-office buyer, invoice recipient and receiving site may be different parts of one purchasing arrangement. Record each role separately before treating an order as ready for dispatch. A familiar group name is not enough to identify where particular items should go.
DROPS gives your team a practical starting point: orders retain the customer association and item details, while catalogue units and packages define the quantities being discussed. Those records help staff compare the actual shop selection with the approved business and destination map.
Company hierarchies, multiple delivery destinations and consolidated billing require separate demonstration; customer-linked orders do not establish a native head-office or multi-branch purchasing system.
Separate four questions
Identify:
- Who is the authorised business buyer for this order?
- Which business should receive the commercial paperwork?
- Who is responsible for the agreed payment arrangement?
- Which site is permitted and prepared to receive each shipment?
The answers may coincide, but do not assume that they do. An invoice email address does not prove the delivery destination, and a site’s usual purchasing contact may not be the person authorised to change a centrally placed order.
Check the arrangement for the actual product, counterparties and jurisdiction. This guide does not establish that a corporate group may redistribute regulated goods among its branches.
Build a compact account-and-destination map
| Role | Record | Check before handoff |
|---|---|---|
| Business buyer | Approved entity and account reference | Correct purchasing relationship? |
| Ordering contact | Contact and stated authority | May approve this selection? |
| Invoice recipient | Business and paperwork destination | Matches the agreed arrangement? |
| Payment responsibility | Agreed responsible business | Any unresolved commercial condition? |
| Receiving site | Approved site reference and destination | Correct and eligible for these goods? |
| Receiving contact | Operational contact and instructions | Site can receive as arranged? |
| Shipment lines | Items, units and quantities for that site | Matches the accepted split? |
Keep the map in your approved business process. It should explain the relationship to the shop order without requiring staff to invent meanings for customer fields.
The UK Government Data Quality Framework recommends documentation that reduces ambiguity and makes records understandable to their users. Clear role definitions serve that purpose here; the map is an original worksheet, not a prescribed account structure. Government Data Quality Framework.
Give each destination its own line allocation
Write down which items and quantities belong to each receiving site. Check that the split reconciles to the agreed total and that units remain consistent.
If one site receives a case and another receives individual units, preserve the conversion basis. Do not rely on “send the rest south” as a shipment instruction.
Keep receiving windows and site-specific instructions with the relevant shipment. A head-office contact’s availability does not establish that every branch can receive at that time.
If the supported ordering process cannot represent the required destinations, resolve the process before accepting that arrangement. Do not assume adding an address in an unrelated note will make the fulfilment record usable.
Hypothetical example: one order, two receiving sites
A fictional head-office buyer approves twenty units of item A. The agreed split is twelve units to Site North and eight to Site South.
The reviewer checks 12 + 8 = 20, then links each destination instruction to its shipment reference. The invoice recipient remains the business named in the agreed paperwork arrangement.
Before dispatch, a site contact requests that all twenty units go north. Staff hold that change for the authorised decision rather than assuming a local receiving contact may override the head-office selection.
This example describes an external business map. It does not demonstrate native split shipping, consolidated invoicing or permission to transfer regulated products between sites.
Check changes against the original arrangement
For a destination or quantity change, record the request, responsible decision-maker and accepted result. Reconcile the revised split and identify which instructions it replaces.
Do not change the business buyer automatically when the receiving address changes. Conversely, an order placed from an old account should not establish that the current entity or contact remains authorised.
Use the wholesale enquiry guide to capture unresolved business requirements before acceptance. For the shop’s customer-facing service scope, the delivery-zone guide provides a separate evaluation path; a geographical match alone does not approve a B2B receiving relationship.
Keep the selected items clear with DROPS
Choose DROPS when you want the customer association, units, packages and ordered items organised in a working shop. Those details give the team a concrete order to compare with the approved buyer, paperwork and destination map.
Explore DROPS and open the demo shops. Bring one fictional head-office order with two proposed destinations. Inspect the catalogue and order records, then demonstrate any required account, address or billing workflow separately before relying on it.