A customer standard operating procedure (customer SOP, sometimes called account instructions or a customer operating manual) is a single, versioned document that tells anyone in your operations team how one customer's freight is handled: who to call, which carriers to book, who pays which charges, what documents are needed and what they are called, how customs is handled, how the account is invoiced, and when a problem must be escalated. The test of a good one is simple: a colleague covering a holiday can book, clear and bill a shipment for that customer on their first day without phoning the account owner. It sits after client onboarding, which collects the information once, and alongside your KPIs, which measure how well you follow it. This post covers the SOP itself.
What a customer SOP is, and what it is not
Forwarders often confuse four documents that do different jobs. Keeping them apart is what keeps the SOP short enough to be used.
- The onboarding checklist is a one-off project: credit application, customs authorisation, contacts collected, first shipment run deliberately. Its output is the raw material for the SOP. Once onboarding is done, the checklist is closed; the SOP lives on.
- The contract and your standard trading conditions set liability, payment terms and legal obligations. The SOP describes how the work is done day to day. It should say plainly that where it conflicts with the contract, the contract governs, and it should never be used to quietly change commercial terms.
- The rate sheet or tariff holds prices. The SOP references it (which version, where it lives) but does not copy prices into its body, because copied prices go stale faster than anything else in the file.
- The customer's own routing guide, common with retailers, is their rulebook for their suppliers and carriers. If one exists, your SOP points to the current version and translates it into your own process rather than retyping it. Our post on retail vendor compliance and chargebacks covers what those guides usually demand.
A common misconception is that an SOP is a quality-manual exercise that only large forwarders need. In practice the smaller the team, the more an account depends on one person's memory, and the more an SOP is worth.
The sections of a customer SOP, at a glance
The table below is a working template. Not every account needs every section at full length: a two-shipments-a-year customer might fit on two pages, while a programme customer with several suppliers and lanes may need an appendix per lane.
| Section | What goes in it | Who confirms it | Gap that causes trouble |
|---|---|---|---|
| 1. Account summary | Customer legal entities, trading names, lanes, modes, typical volumes, services in scope and out of scope | Account owner | No one knows which entity is the importer or the bill-to party |
| 2. Contacts and escalation | Named contacts by role on both sides, out-of-hours contact, escalation ladder, approved channels | Customer and account owner | Only one contact, who is on leave when the hold happens |
| 3. Booking rules and carriers | Preferred and excluded carriers, whose contract is used, cut-offs, routing or transshipment limits, approval needed for spot rates | Customer logistics lead | Booking on the cheapest sailing when the customer wanted the direct service |
| 4. Incoterms and who pays what | Incoterm per supplier or lane, named place, a charge-by-charge split of who pays | Customer and, where relevant, their suppliers | Origin charges billed to the wrong party |
| 5. Documents and naming | Required documents per mode, who supplies each and by when, file naming rule, where files are stored | Customer and operations | Late commercial invoice, documents nobody can find |
| 6. Customs instructions | Broker of record, authorisation status, classification rules, product library, licences, permits, special programmes | Customer's trade compliance contact | Operator guesses a classification under deadline pressure |
| 7. References and PO numbering | Reference formats and where each must appear | Customer | Invoices rejected for a missing PO number |
| 8. Invoicing and billing codes | Billing entity, charge codes mapped to customer cost codes, consolidated or per-shipment billing, supporting documents, disbursement rules | Customer accounts payable and your finance team | Invoices queried and paid late |
| 9. Exception thresholds | Numeric triggers for notifying or escalating, and to whom | Customer and account owner | Customer hears about a delay from their own client |
| 10. KPIs and reporting | Which measures, how each is defined, report format, cadence, review meetings | Customer and account owner | Arguments over what "on time" means |
| 11. Version control | Version number, effective date, owner, change log, sign-off record | Account owner | Two versions in circulation, neither agreed |
Writing the sections that cause the most trouble
Contacts and escalation
List contacts by role first and name second ("customs approvals: trade compliance manager, currently ..."), so the section still makes sense after staff turnover on either side. For each role give the channel the customer actually wants used. Include an escalation ladder with at least two levels on each side and an out-of-hours route if the account ships time-critical cargo.
Add one rule that has nothing to do with freight and everything to do with fraud: any request to change bank details, billing addresses or delivery addresses is confirmed by a call to a number already held on file, never to one supplied in the same email. Our guide to business email compromise in freight explains why that rule belongs in writing.
Booking rules and preferred carriers
Say which carriers are preferred, which are excluded and why, and whose contract a booking moves under (the customer's own contract or your rates). If the customer has a named-account or contract number with a carrier, record it and who is allowed to use it. Then add the decisions an operator would otherwise have to make alone: is transshipment acceptable on a given lane, is a slower service acceptable to save cost, what is the latest point at which a booking can be made, and above what price or outside which service an operator must get approval before confirming. "Book the best option" is not an instruction; "direct services only on the Asia to North Europe lane, spot above the agreed rate needs written approval from the logistics manager" is.
Incoterms and who pays what
Record the Incoterm and named place for each supplier or lane, not one term for the whole account, because programme customers often buy on several terms at once. Then go further than the term. Incoterms allocate costs and risk between buyer and seller in broad terms, but your invoice is made of specific lines, and how a particular charge such as terminal handling is treated can depend on local practice and the parties' contract. A short charge-split matrix (each charge type down the side, payer across the top) removes the guesswork. Our guide to Incoterms 2020 explains each rule; the SOP only needs to record which rule applies and how the customer wants the edge cases handled.
Document requirements and naming
List the documents required per mode, who supplies each, and the deadline relative to the cargo milestone (for example, commercial invoice and packing list before the booking is confirmed, not after the vessel sails). If the customer supplies shipping instructions, point to what they must include; our shipping instructions template covers that.
Set a file naming rule and a single storage location. A pattern such as CUSTOMERREF_PO_DOCTYPE_YYYY-MM-DD works because it sorts correctly, survives being emailed and tells anyone what the file is without opening it. Writing dates year first (the ISO 8601 order) avoids the day-month confusion that plagues international teams. Whatever pattern you choose, write two or three worked examples into the SOP; people copy examples, not rules.
Customs instructions and broker details
Name the broker of record for each country of import and the status of the authority to act. In the United States, a customs broker must obtain a valid power of attorney before transacting customs business for a client and keep it with its records (19 CFR 141.46); CBP Form 5291 may be used, or another written power of attorney in equivalent terms (19 CFR 141.32). In the UK, GOV.UK guidance states that a representative cannot act without written instructions and that those instructions must show whether the representative acts directly or indirectly. The SOP should record which arrangement is in place and when it was last renewed, not reproduce the authority itself.
The most important customs line in most SOPs is about classification: who decides tariff classifications, where the approved product library lives, and what an operator does when a new product appears. The answer should never be "the operator picks a code under deadline pressure". Note also how long records must be kept; for US imports the general rule is five years from the date of entry (19 CFR 163.4). If you are unsure where broker duties stop and forwarder duties start, see do you need a customs broker.
PO and reference numbering
State each reference format the customer uses (purchase order, shipment or load reference, cost-centre or project code) and exactly where each must appear: house bill of lading, commercial invoice, your invoice, pre-alerts, carton labels, advance shipping notices. A missing reference is one of the most common reasons an otherwise correct invoice sits unpaid in an approval queue.
Invoicing rules and billing codes
Name the billing entity and address, the invoice format, whether billing is per shipment or consolidated, the currency, and which supporting documents must be attached. Map your charge codes to the customer's cost codes so the same charge is always coded the same way, and say how duties, taxes and other disbursements are recharged. Your internal job costing is a separate matter; the SOP records what the customer needs to see.
Exception thresholds
An exception section that says "keep the customer informed" will be ignored. Agree numbers. For example: notify the customer the same working day when estimated arrival moves by more than an agreed number of days; get written approval before accepting any cost more than an agreed amount above quote; escalate any customs hold, cargo damage or temperature excursion immediately to the named contact; warn when demurrage or detention free time is within an agreed number of days of running out. The numbers are the customer's to choose, which is exactly why they belong in an agreed document rather than in an operator's head. The shipper-side view of the same process is in our freight exception escalation playbook, which is worth sending to customers who have never thought about their own thresholds.
KPIs and reporting cadence
Do not invent new measures here; pick the ones that matter to this customer from the set you already track and, critically, write down how each is defined. "On time" against the carrier's schedule, the quoted transit time or the customer's required date are three different numbers. Record the report format, the day it goes out and the cadence of review meetings. How to define and calculate the measures themselves is covered in the KPI post linked at the top of this guide.
Keeping the SOP versioned and agreed with the customer
An SOP is only useful if everyone is reading the same version and the customer has agreed to it. The mechanics are simple and borrowed from any quality system; ISO 9001, for example, asks organisations to control documented information, including distribution, access and version control. You do not need certification to use the discipline.
- One master, one location. Keep the editable master in one place and distribute read-only copies. Link to it from the customer record in your forwarding system so operators reach it from where they work.
- A front page that carries control data. Version number, effective date, document owner, next review date and a one-paragraph summary of what changed.
- A change log. Each change dated, with who asked for it and who approved it. "Per customer email 3 March" is enough, provided the email is filed.
- Customer sign-off. A signature or a written email acceptance of the specific version number. Without it, a disputed instruction becomes your word against theirs.
- Review triggers as well as a calendar. Review at least once a year, and also whenever a new lane, supplier, mode, broker, carrier contract or key contact appears, or after any significant exception.
- Retire old versions. Mark superseded copies clearly and remove them from shared folders. An old version still in use is the most common way a well-run SOP fails.
Instructions also arrive by email between reviews ("from next month, please route via ..."). Make it someone's job to fold those into the SOP within a set number of days, or the document drifts away from reality and the team learns to ignore it.
Why customer SOPs fail
The SOP nobody reads
The usual causes are length, generic wording copied from another account, and being stored somewhere nobody looks. Fixes that work: put a one-page summary of the account's "must know" rules at the top; cut anything that is true of every customer and move it to your general procedures; link the SOP from the booking screen; and test it by having an operator who does not know the account run a shadow booking from the document alone. Every question they have to ask is a gap in the SOP.
The tribal-knowledge account
This is the account that works perfectly because one experienced operator knows every preference, and breaks the week that person leaves, goes on holiday or is off sick. The customer then experiences a sudden fall in service with no change in price, which is how accounts are lost. The fix is structural: every account has a named second operator who handles real shipments regularly, and the SOP is written or rewritten as part of any handover, while the person who knows the account is still there to answer questions.
The SOP that promises what you cannot deliver
Sales sometimes agree service levels the operation has never run. Have operations read and sign off the SOP before it goes to the customer, and do not commit to a threshold or report your systems cannot produce.
What to do next
- Pick your two largest accounts and your most person-dependent account, and draft an SOP for each using the eleven sections above.
- Run a shadow booking on each with an operator unfamiliar with the account, and fix every gap they hit.
- Send each SOP to the customer as a numbered version, ask for written acceptance and file it with the change log.
- Set a review date and assign a second operator to each account so the knowledge is never held by one person.
If you are building out the accounts that will need these SOPs, more than 29,300 logistics companies are searchable by country and service in the CargoLinked directory, and the public requests board lists freight that shippers have posted for forwarders to quote on directly.
This article is general information about operating practice, not legal, tax, financial or customs advice. Customs, record-keeping and representation rules vary by country and change over time; confirm the current requirements with the issuing authority or a licensed customs broker or other qualified professional before relying on them.
