
A year's trade in eight weeks
The client assembles Christmas gift packages for children: sweets, fruit, a small gift and a bag. Its buyers are mostly organisations. Companies buy for their employees' children, and kindergartens and schools buy for their pupils. One order can be 15 packages or 5,000, often for several sites, and every package has to arrive before a fixed day in early December.
Almost the whole year's work happens in about eight weeks. In that time the business handles between 80,000 and 100,000 individual packages. From the office side, one administrator runs it.
What a webshop could not do
A webshop sells a fixed product to one buyer, with one invoice and one delivery address. Here almost nothing is fixed.
The buyer shapes the package
Organisations rarely click "buy". They ask for a quotation, often with a budget and a few wishes: no nuts, more chocolate, a better gift for the older children. The administrator answers with several versions of the package side by side. In each version some contents can be swapped for an alternative, the buyer picks one gift from a list, and chooses a bag. The prices update as the buyer chooses. The buyer compares the versions on one private page, downloads them as a PDF to show colleagues, and sends back the choice with one button. The choice becomes part of the order.
One buyer, many addresses, many invoices
A company may pay from one office and deliver to several sites. The system keeps several billing and several delivery addresses for each customer, and an order can be split between addresses after it was placed. Invoices are issued through the client's online invoicing service and follow the way organisations pay: a payment request, an advance invoice, then a final invoice that deducts the advance. Open invoices can be paid by card through a secure link.
Delivery in bulk, or one by one
Packages go out in three ways. The client's own vans deliver on planned routes, with each van's crate capacity taken into account. The GLS courier takes them either as one shipment or literally one parcel per address, with labels made by the system and the delivery status read back automatically. Buyers can also collect from pickup points. The system records the crates and boxes for each package and each address, so packers know how to pack for every site.
What Addmonte built
Quotations prepared by AI, approved by a person
Enquiries arrive through the website and by e-mail. The system reads the office mailbox, recognises which letters are requests, links each reply to its case, and drafts the answer in the office's own writing style. It asks the buyer only what an offer needs: how many packages, which package or what budget, how many addresses, and by when. When nothing is left to ask, it proposes package contents from the components actually in stock and within the buyer's budget. For a returning customer it starts from last year's order. Nothing goes to a customer without the administrator's approval: the system prepares, the person decides.
Stock that shows what can really be sold
For every component, the system counts four figures: what is on the shelf, what packing batches have already claimed, what confirmed orders still need, and what quotations sent but not yet accepted would need. The difference is the expected free stock. It appears next to every component wherever the administrator picks one, for a quotation, an order or a package recipe. A negative figure is shown in red before the component is offered, not after it is sold.
The shopping list gives two buying suggestions side by side: what the confirmed orders need, and what the open quotations would add. The person in the wholesaler decides between them.
Packing planned against stock, deadlines and distance
Orders are prepared for packing in batches. A batch claims stock in the order it was created, and the system shows which orders in it are fully covered and which are short, and of what. The administrator sends the covered orders to the packers. Short orders wait without losing their place.
The system also puts every confirmed order on a packing day. The latest day is three days before the order's delivery deadline. The earliest day leaves three working days for buying the components. Each day has a capacity that rises towards December. Van deliveries go on a day that already has an order within 30 km. When a day is full, the order moves earlier, never later.
Packers work from their own screen: a list ordered by delivery deadline, with a printed slip for each order. When an order changes after its slip was downloaded, the list marks it, so nobody packs from an old slip.
Saving where it helps, confirming where it matters
In the peak weeks the administrator makes hundreds of small changes a day: a quantity, an address, a delivery window, a component. On most screens there is no Save button. As in an online spreadsheet, a change is saved a moment after the administrator stops typing, a small marker confirms it, and on the main screens the last changes can be undone with one click. On a long page nobody has to scroll back to find a button, and nothing is lost by moving on.
We watched the office at work for several weeks. In the peak season the administrator makes at least 600 to 800 changes a day. Finding and pressing a Save button on a long page takes at least two seconds each time, often more. By that conservative estimate, saving without a button gives the administrator back 20 to 30 minutes a day.
Where a step cannot be taken back, the system asks first. Creating a record, deleting one, issuing an invoice, and sending an e-mail or a text message to a customer each have their own button and a confirmation. Which screen works which way was decided step by step, from how the office actually works.
Two assistants that never need retraining
Buyers can ask a chat assistant on the website about packages, contents, prices and delivery. It does not answer from a copy made at some point in the past. Each time it answers, it reads the current packages, prices and swap options straight from the live system. A price changed in the admin, or a package taken off sale, is in its next answer, with nothing to re-teach.
The administrator has an assistant of their own, which answers questions about how the system itself works: which screen does what, in which order, and why. It answers from the system's handbook, and every new feature arrives with its own handbook chapter, which reaches the assistant automatically with the release. When the system changes, the assistant knows the new way of working from the day the change goes live. For a business run by one administrator, it replaces the colleague who could otherwise be asked.
One system, one season
Behind all this sit a warehouse of components with stock and price history, package recipes, the customer register, delivery notes with QR codes, a feedback survey after delivery, and season reports.
In 2026 Addmonte rebuilt the system on a current platform. Every record of the previous system was moved across one to one, and every old web address still works. Addmonte has built and run this client's system since 2011.
Results
One administrator handles between 80,000 and 100,000 individual gift packages in an eight-week season.
By a conservative estimate from several weeks of observing the office, saving without a button gives the administrator back 20 to 30 minutes a day in the peak season.
More case studies
Similar requirement?
Tell us how your business works today. We’ll tell you honestly whether we’re the right fit.



