Delivery instructions and order notes at checkout: mistakes
Short answer: A free-text "order notes" box at checkout seems simple, but notes often never reach the person who needs them: the driver, the kitchen or the packer. Decide what information you actually need, use specific fields where you can (a safe-place choice, a delivery date, a gift message) rather than one catch-all box, place them where customers will see them, and make sure each one flows to the right screen, label or ticket. Then check that it's actually read.
"Leave it with the neighbour at number 12." "No onions." "Please don't ring the bell, baby asleep." Customers type these notes trusting someone will read them. In many small online shops and food businesses, nobody does, because the note sits in an order record that the person packing or delivering never opens. Here are the mistakes behind that, and what to do instead.
Mistake 1: One vague box for everything
A single field labelled "Order notes (optional)" gets everything: delivery instructions, allergy details, gift messages, questions about stock, and complaints about the last order. Staff can't route it, so it gets skimmed or ignored.
Instead: split the most common needs into specific fields:
- Delivery instructions (where to leave it, access codes, best entrance);
- Gift message, if you offer gift wrapping;
- Preferred delivery date or time slot, as a picker rather than text;
- a smaller "Anything else?" box for the rest.
Both major platforms support this. Shopify's theme documentation describes cart notes (a text area named note) and separate cart attributes for capturing additional, named pieces of information. WooCommerce's developer documentation for the block checkout describes registering additional fields in contact, address or order-information sections, and gives "How did you hear about us" and "Gift message" as examples of order-information fields.
Mistake 2: Putting the field where nobody looks
A notes box hidden at the bottom of the cart page, or behind an "add a note" link, is missed by most customers, and found only by those who scroll around.
Instead: place delivery instructions next to the delivery address, where people are already thinking about delivery. Gift messages belong next to the gift option. If the field is in the cart rather than the checkout, make sure customers who use express checkout buttons don't skip past it entirely.
Mistake 3: Using notes for safety-critical information
Food businesses sometimes rely on a free-text note for allergies. A note can be missed, misread or abbreviated on a kitchen ticket.
Instead: if allergens matter to your business, handle them with structured options and a clear process in the kitchen, not only a note field. Make sure customers can see the information you're required to provide, and check the rules that apply to your business. The note field can supplement, never replace, that process.
Mistake 4: The note never reaches the driver or packer
This is the core failure. The note is saved to the order, but the packing slip, delivery app, kitchen printer or courier label doesn't show it.
Instead: trace each field from checkout to the person who acts on it:
- Does the packing slip template include the note and gift message?
- Does the courier integration pass delivery instructions to the carrier's label or app? Many courier services have a dedicated instructions field, often with its own length limit.
- Does the kitchen ticket or order display show notes prominently?
- Does your delivery driver app or route sheet show them?
Place a test order with distinctive text ("TEST NOTE – PLEASE IGNORE") and follow it through every step. Wherever the note disappears, that's what to fix.
Mistake 5: No length limit, or a hidden one
Some customers write paragraphs; some courier systems cut instructions off after a fixed number of characters. The result is "Leave with neighbour at num".
Instead: set a sensible character limit on the field that matches the shortest system it feeds, show a character counter, and write helper text with an example: "e.g. Leave in the porch, side gate code 1234." The HTML maxlength attribute on a text input or textarea enforces this in the browser; validate on the server too.
Mistake 6: Inviting questions you won't answer
"Any questions? Leave them here" turns the notes field into an unmonitored inbox. Customers ask about delivery times or substitutions and wait for replies that never come.
Instead: don't invite questions in the order notes. Link to a contact method near the field ("Questions about your order? Message us"), and if someone does ask a question in a note, have a process to spot and answer it.
Mistake 7: Collecting personal details you don't need
Notes fields collect phone numbers, door codes and health details. Some of that is necessary for delivery; some isn't.
Instead: ask only for what helps you fulfil the order, avoid prompting for sensitive details, and treat access codes like any other personal data, visible to the staff who need them and not printed on the outside of parcels.
Mistake 8: Never reviewing what customers write
Patterns in notes tell you what your checkout is missing. If dozens of people write "please deliver after 5pm", you need a time-slot option. If many write gift messages in the general box, you need a gift field.
Instead: export a month of notes and sort them into themes. Turn common themes into proper options.
A quick setup checklist
- Specific fields for delivery instructions, gift messages and dates where relevant.
- Fields placed next to the related choice (address, gift option).
- Character limits matching the systems downstream, with a counter and example.
- Notes visible on packing slips, kitchen tickets, labels and driver apps, tested end to end.
- No promise that notes are a support channel.
- Allergy handling through structured options and process, not only notes.
- Monthly review of note themes.
FAQ
Is the cart page or the checkout the better place for notes?
Near the related information, usually checkout next to the address. If your platform only supports cart notes, make sure express checkout users can still add them.
Can couriers see my customers' notes?
Only if your shipping integration passes them to the courier's system. Test with a real label.
How long should the delivery instructions field be?
Match the shortest downstream limit, often the courier's instruction field. Check your carrier's settings.
Should notes be required?
Usually not. Optional fields with good examples work better than forcing everyone to type something.
If your customers' delivery notes seem to vanish before the doorstep, tell us which shop and courier tools you use and we'll help trace where they get lost.