Logging damage and breakage.
Separate reason code, do not book as sold or returned.
support/pos-retail/schadebreuk-registratiesteps: 5
Try this first
- Create distinct reason codes (breakage, theft, damage, expired)
- Do not book as sale, that breaks VAT
- Do not book as return, that gives a false revenue correction
- Keep damage photos for insurance claim
- Monthly damage-rate report per category
When to bring us in
Damage rate rising without clear cause? Process review, often it is transport or storage.
See also
- Lightspeed Retail or K-Series?Retail is for SKU-driven shops with e-commerce, K-Series is for hospitality.
- Is MplusKASSA right for my shop?Dutch vendor, strong for multi-store retail with solid accounting integration.
- Cloud POS or local only?Cloud needs reliable internet plus 4G failover, local-only loses multi-store sync.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.