How a simple delivery note can prevent expensive confusion in a small business

A delivery note solves a different problem from an invoice

An invoice answers a commercial question: what is being charged and how much is due. A delivery note answers an operational question: what physically moved, from whom, to whom, when and in what quantity. Small businesses often blur those jobs because the same order, customer and products appear in both documents. That shortcut creates trouble when a delivery is partial, a price changes later, goods are handed over before invoicing, or the recipient disputes what actually arrived. Keeping the delivery document separate gives both sides a clean handover record without forcing the document to pretend that a tax or accounting event has already occurred.

Capture the facts before the goods leave

The strongest document is created before memory starts filling gaps. Give the document a clear reference, record the date and relevant dispatch or handover time, identify the sender and recipient, state the delivery address, and list every item with a recognizable description, SKU where useful, quantity and unit. Add transport details only when they matter: carrier, driver, vehicle, tracking reference, packages or total weight. The goal is not to make every delivery note enormous. The goal is to include the information that somebody would need if the truck is delayed, a box is missing, the warehouse received the wrong quantity, or the customer asks what was actually sent.

• Document number or reference that can be found later
• Sender, recipient and delivery destination
• Dispatch or handover date and relevant time
• Item description, SKU, quantity and unit
• Carrier, tracking, vehicle, package or weight data when relevant

Use one document for one handover event

A common source of confusion is editing yesterday's file until it looks like today's delivery. That destroys history. A better workflow is to create a new document for each handover and treat corrections as revisions rather than silent replacements. If six products were planned but only four were loaded, the delivery record should describe the four that actually moved. If the remaining two go tomorrow, create another handover record. This makes stock checks, customer conversations and later reconciliation much easier because the paper trail follows reality instead of the original intention.

Country rules belong to the document country, not the interface language

A Russian-speaking entrepreneur can create a document for a delivery in Israel, a Hebrew-speaking company can ship to Germany, and an English interface can be used for a French transaction. That is why 5SOLO separates the language of the interface from the country profile of the document. The country profile is a checklist for fields and terminology that may matter in that market; it is not a legal certification. Local bookkeeping, tax, transport and record-retention rules can change, so the final responsibility remains with the business and its professional advisers. The practical benefit is still significant: a country-aware form reduces the chance that an obvious local field is forgotten simply because the user works in another language.

A repeatable handover process is more valuable than a perfect one-off form

The business value appears when the same discipline is used every time. Prepare the sender profile once, keep recipient details consistent, create the goods list, verify quantities at loading, generate the PDF, and have the recipient review the same information at delivery. When something changes, update the document before the handover rather than explaining the difference later in chat messages. This process reduces the number of situations where operations, sales and the customer are looking at three different versions of the truth.

• Prepare the document before dispatch, not after a dispute
• Verify actual loaded quantities against the document
• Keep the PDF or printout that corresponds to the real handover
• Use a new document or explicit revision when facts change
• Keep invoices and tax documents in the accounting workflow where they belong

Where the 5SOLO delivery tool fits

The new 5SOLO delivery module is deliberately independent from the project-cost calculator. It keeps its own local draft, supports delivery notes and goods handed over for sale, accepts multiple product lines, lets you add requested prices when the commercial model needs them, and supports custom fields for information that is specific to your operation. The PDF view is separate as well, so the document can be reviewed as an A4 handover record rather than inheriting fields from an estimate. That separation keeps the tool simpler: one engine deals with project pricing, the other deals with physical goods and their transfer.