
If you're opening a luggage-storage business and you're not running on dedicated software, you'll end up running on Wix for the site, Stripe for cards, Google Sheets for bookings, a notebook for locker codes, your personal phone for customer questions, and your own brain for everything else. We've watched a hundred operators do this. It works for the first three months, costs you weekends from month four, and becomes unmanageable by month six.
This guide explains what luggage-storage software is for, what to look for when you evaluate one, and which decisions are worth obsessing over and which aren't.
What luggage-storage software actually does
A complete platform handles six jobs. If any one of them is missing, you're going to end up stitching it together with another tool — which is the failure mode this guide is trying to help you avoid.
1. The booking storefront. Where customers land, choose a size, pick dates, pay and receive their access details. This is your shop window. If you franchise, the marketplace is your storefront. If you go independent, this is the page that ranks on Google for "luggage storage [your city]" and converts visitors into bookings.
2. The locker hardware controller. The software talks to the physical locker. It generates the access codes, opens the locker remotely when the customer is locked out, logs every open/close event, and reports hardware errors before the customer does. A platform without remote locker control means every problem becomes a physical store visit.
3. Payment orchestration. Cards, Apple Pay, Google Pay, iDEAL in the Netherlands, Bancontact in Belgium, Bizum in Spain. Refunds, retries on failed payments, payouts to your bank, reconciliation with your accounting. Modern luggage-storage software is built on Stripe Connect or equivalent — you sign up once, the platform handles the rest.
4. Operations dashboard. Live view of what's in every locker, who paid, what's overdue, who's about to arrive. Staff vs. owner roles. Audit trail of every privileged action. This is where you spend most of your time once you're operational.
5. Customer communications. Confirmation emails, PIN reminders, post-stay review prompts. The good platforms also include a WhatsApp AI agent that handles 80–90% of inbound customer messages in any language without a human in the loop. The handful that don't include this leave you doing customer service from your phone all day.
6. Reporting and tax. Daily revenue, occupancy, refund rate, NPS, review averages. Plus tax-ready invoice exports in the format your accountant wants (Spain, France, Germany and Italy all have their own quirks).
The first time you read that list it feels like an exhaustive feature dump. It isn't. Each of those is a job-to-be-done. If your software solves five of them and you bolt on something else for the sixth, you've created a sync problem and a future migration headache.
Stitching free tools vs. an integrated platform
The most common path operators take in the first year is the worst one for the second year. Here's the typical stack we see when we onboard an operator who has been running for six months:
- Wix or Squarespace for the customer-facing page (no booking flow; sends visitors to WhatsApp)
- Personal WhatsApp number for booking requests
- Stripe payment links sent manually one at a time
- A spreadsheet to track which locker is occupied
- Sticky notes for PIN codes
- Holded or QuickBooks for invoices (filled in by hand)
- Personal email for review requests
This stack has zero up-front cost. It also has a hidden running cost in the operator's time that nobody adds up until they're drowning. We've measured operators spending 25–35 hours a week on customer-service ops once they cross 50 bookings a week. At a self-imposed €15/h opportunity cost, that's around €1,700/month going into the swivel chair.
A dedicated platform replaces all of that for €49–€299/month plus a small per-booking fee. The break-even is almost immediate.
Evaluation criteria that actually matter
When you're comparing platforms, almost every vendor will check the basic boxes on the storefront and the operations dashboard. The differences that determine whether you'll be happy in eighteen months are usually buried.
White-label, not just a logo swap. Some platforms call themselves white-label and mean they'll let you upload a logo. The serious ones let you serve on your own domain (booking.yourshop.com), with your DKIM/SPF on the confirmation emails, your VAT number on the invoices, and your brand on the PIN screen at the locker. The difference matters for SEO (your own domain ranks, not the platform's) and for owning the customer relationship.
Remote locker control. You can open, lock, override, audit any locker from a phone. If the platform requires you to physically be at the locker bank to clear a stuck door, you'll resent it after the first 11pm call.
Multi-channel booking. Web, on-site kiosk, WhatsApp. The kiosk lets walk-ins convert without your help. WhatsApp absorbs 80–90% of inbound messages with an AI agent in any language. If a vendor only supports web bookings, you'll be on your phone all day handling questions that should auto-resolve.
Languages — operator's choice, not the platform's. Tourist customers come in every language. A platform that gives you six fixed languages won't serve a Korean customer in your Madrid store. The serious platforms let you serve any languages you want on the storefront and kiosk, with an AI WhatsApp agent that accepts any language in the world without configuration.
Real integrations with the rest of your stack. Stripe Connect on your account (not theirs — important for PCI scope and payout speed). Google Business Profile sync for reviews. Push to your accounting tool (Holded, Sage, QuickBooks). Webhook out to anything else. If the platform only lets you export CSV monthly, you're going to manually re-enter every booking into your accountant's tool.
Pricing rules that match real operations. Time bands. Size mix. Peak surcharges. Multi-day discounts. Promo codes. Family bundles. Sponsor-funded zeros for events. If the platform offers "fixed price per booking", you'll lose 15–25% of margin to the operators who can flex.
Compliance built in. EU-compliant invoicing for Spain, France, Germany and Italy (each has its own format). GDPR-clean data hosting in EU regions. A signed DPA you can show your privacy officer. Some platforms still ship "compliance as your problem" — that's a hidden cost.
Roles and audit. Floor staff see today's bookings. Store managers see one store's history. You see everything. Every privileged action goes into an audit log. If the platform only has one access level, scaling to two stores becomes a security and HR problem.
What to skip in evaluation
Some things vendors will pitch as features rarely matter in practice. Save your evaluation time:
- App downloads for customers. Customers don't want an app for a 4-hour transaction. Browser + WhatsApp covers it.
- "AI for everything." AI booking concierge is genuinely useful (it's a chatbot that books lockers); AI for "predictive analytics on your business" is generally a presentation aid, not a tool you'll use weekly.
- Native integrations with marketplace X. Webhooks and a clean REST API beat 30 pre-built integrations you don't need. Make sure the API exists.
- Per-locker pricing. Most platforms now offer a revenue-share alternative that costs less for stores with low fixed locker count but high turn rate.
A quick scoring framework
If you're between two finalists, score each on a 1–5 scale across these criteria and weight by what matters most to you. Our customers' usual top three weights are:
- White-label end-to-end — without this, you don't own your business in any meaningful sense
- Remote locker control + automation — saves the most operator time per week
- Multi-channel booking with WhatsApp AI — handles peak inbound without staff
A platform that scores 4+ on those three is one you can grow on for years. A platform that scores 3 or less on any one is a platform you'll outgrow.
Migration considerations
If you're already running on a stitched stack and considering moving to a dedicated platform, the migration is shorter than you'd guess. On a typical timeline:
- Day 1: Demo, see your numbers modelled.
- Days 2–5: Branding (logos, colours, copy, domain) + locker hardware config.
- Days 5–7: Stripe Connect setup, payouts to your bank, test bookings.
- Days 7–10: Real bookings on the new system; old system in read-only mode for any in-flight customers.
- Day 10+: Decommission the old stack. Keep the spreadsheet as a backup for 90 days.
The single thing that goes wrong most often during migration is locker hardware compatibility. Confirm with your platform vendor up-front which manufacturers they support; budget for adapter hardware if you have an unusual setup.
What to take to the demo
When you book a demo with any platform, ask three questions that vendors who haven't actually built the thing struggle to answer well:
- "Show me a real customer's dashboard with the live data on it." If the answer is a Figma mock-up, you're being sold vapourware.
- "What happens at 11pm when a customer's PIN doesn't open the locker?" The answer should involve sensor recheck, automatic recovery, and only paging you if a human is genuinely needed.
- "How do I cancel?" Healthy vendors answer this without flinching. Defensive answers mean lock-in.
Most operators we talk to end up with two or three serious finalists after a week of evaluation. Picking among them is mostly about fit with your operating style — the technology gap between the top vendors is smaller than the gap between any of them and a stitched DIY stack.
If you want to see LockMe in that comparison, book a 30-minute walkthrough. We'll model your operation on the platform — your numbers, your city, your hardware — before you commit to anything. And if you'd like to think about the franchise question first, our franchise-vs-independent comparison is the natural prerequisite to this guide.
