| Family with three children at two schools | Three separate orders typed in | One order, packed per student | Each line is linked to a student profile, so packs are labelled by child and delivered to the right place. |
| New school list released in November | Retyped from a PDF | Loaded from a structured list | The list is imported, titles are checked against availability, and the school approves a preview before it opens to families. |
| Out of print title on a booklist | Found when packing in January | Flagged before the list goes live | Availability is checked against supplier data when the list is loaded, and the school is asked for a replacement early. |
| January rush at the shop | Long queues and empty size runs | Pre orders, slots and live stock | Pre season orders spread the load, collection slots limit queues, and stock buffers protect walk in customers. |
| Bulk delivery to a primary school | Teachers sort a pile of bags | Packs labelled by class | Orders marked for school delivery are packed and labelled by year level and class, with a manifest for the school office. |
| Wrong size before term starts | Refund and reorder, stock lost track of | Linked exchange | The return and replacement are linked, the returned item is restocked if resaleable, and the family is not charged twice. |
| School adds a new sports polo | Website and POS updated separately | Added once, published to both | The new garment is set up in the inventory system against the school and appears online and at the counter together. |
| Parent asks what data you hold | Searched across several systems | One family record to export or delete | Student information is held in one place with a defined retention period, so access and deletion requests are simple to fulfil. |