SaaS vs Custom

Brisbane hospitality laundry service. 3 vans. 40+ hotel/hospital clients. 8,000+ linens processed daily (bed sheets, pillowcases, towels, chef uniforms, surgical linens). Current workflow: (1) Hotel calls Thursday morning "We need pickup Monday + Wednesday." Coordinator (Jessica) writes on whiteboard. Monday 6am: driver 1 arrives hotel, loads 500 soiled linens into van (no count, no barcodes — driver eyeballs "looks about right"). Driver 2 delivers 500 clean linens from Friday's batch (also eyeballed). Hotel manager counts bins: "Hm, looks like 50 towels short?" Jessica checks Filofax (actual paper note system, yes really), finds 3 hotels needing Monday pickup, can't match which pickup has which inventory. Linens get mixed between hotels. Hotel A gets 20 of Hotel B's branded pillowcases. (2) Washing process: 8,000 linens dumped into industrial washers, sorted by fabric (colours, whites, delicates). Nobody tracks which linen belongs to which hotel. Linens get damaged (one hospital says 150 surgical linens "go missing" per month — staff steals? Mixed in laundry? Nobody knows). (3) Billing: Jessica manually invoices each hotel monthly: "Hotel A: 22 pickups × $180 = $3.96k. Damaged linens: 5 sheets × $40 = $200. Total $4.16k." Hotel A disputes: "You invoiced us for 22 pickups but you only came 20 times." Jessica checks whiteboard (faded notes from 3 months ago), can't verify. Dispute unresolved, hotel withholds payment $2k. (4) Driver routes: Jessica plans routes by gut feel. Van 1 goes Fortitude Valley → Southbank → West End (2 hours driving, 8 pickups). Van 2 goes Kangaroo Point → Bowen Hills → New Farm (1.5 hours driving, 12 pickups). Unoptimised — driver 1 could combine 2 trips into 1, save 45 mins/day × 5 days = 3.75 hrs/week labour. (5) Lost items: Hotel C claims "We're losing $800/month in branded linens." No tracking. Laundry can't prove linens were received or identify where they disappeared.

Six Features Custom Platform Delivers

1. Per-Item Barcode Tracking — QR Code Scan at Pickup/Delivery, Item Provenance Audit Trail, Lost-Linen Recovery

Custom system: [Barcode Warehouse]. Every linen item (sheet, towel, uniform, surgical) gets a unique barcode label (printed thermal label, waterproof, survives 500+ washes). Hotel A bed sheet: barcode QR-HTLA-BS-00847. Barcode database: item type (bed sheet), size (queen), fabric (Egyptian cotton), hotel (Hotel A), original cost ($85), expected lifespan (500 washes), current wear level (0%, new). Monday 6am pickup: driver scans hotel environment. Coordinator Jessica (or driver via mobile app) scans arrival at hotel: QR-HTLA-BS-00847 enters system, timestamp 6:15am, GPS location "Hotel A, Level 3 Linen Room, -27.4698, 153.0251". Driver loads van. 40 items from Hotel A: driver scans each barcode, system logs: "QR-HTLA-BS-00847, QR-HTLA-BS-00848, ..., QR-HTLA-TW-01203 (40 items). Driver 1 Van Load 2024-06-10-MON-001: 40 items from Hotel A, weight 18kg, departure 6:35am." Driver arrives laundry facility, unloads. Coordinator scans unload: "Van Load 2024-06-10-MON-001 received at facility, 40 items counted, QC check: all items match barcode list (0 discrepancies)." Items go to washing queue. System tracks: "QR-HTLA-BS-00847 washed 6:45am–8:15am, temperature 60°C, whites cycle, fabric OK." Item emerges, scanned again: "QR-HTLA-BS-00847 post-wash, 6 months wear (now 506 lifetime washes complete, 1/500 expected life consumed)." Item folded, loaded into clean-bin for Hotel A. Wednesday 8am delivery: driver scans leaving facility, scans each item into delivery bin. Arrives Hotel A, scans delivery: "Van Load 2024-06-12-WED-002 delivery, 40 items from Hotel A, expected: QR-HTLA-BS-00847, QR-HTLA-BS-00848, etc. Actual: 39 items (1 missing)." System flags: "QR-HTLA-BS-00850 expected in delivery but not scanned. Status: in-transit, last known at facility 8am Wed." Jessica checks wash logs: "QR-HTLA-BS-00850 washed, post-wash scan confirmed, but not scanned into delivery bin." System shows: "Item last location: clean linens staging area, 7:50am Wed. Item probably left in staging, not loaded into van." Jessica checks staging area, finds QR-HTLA-BS-00850, scans it into delivery. Hotel A delivery completed: 40 items delivered, scanned by hotel manager on arrival. System closes: "Hotel A Wed delivery complete, 40 of 40 items delivered, timestamp confirmed, signature digital-signed by hotel manager." Hotel A invoice: "Delivery confirmed: 40 items × $0 (service fee, not per-item). Weekly pickup/delivery: $450. Damaged items: 0. Lost items: 0." Zero disputes. System audit trail for Hotel A: "Jan–Jun 2026: 480 items delivered, 479 items accounted for (99.8% recovery), 1 item lost (QR-HTLA-PW-00322, lost in-transit May, $85 cost, charged to insurance claim, not invoice)." Damaged items: system tracks wear. QR-HTLA-BS-00847 shows: "Wash count: 506/500 expected. Wear level: very high. Recommend retirement." Jessica marks item as retired before next wash. System alerts: "Hotel A: 2 items near end-of-life this month. Recommend replacement order." Hotel A orders 2 new sheets. Value: barcode tracking eliminates "lost linens" mystery (provenance documented), prevents invoice disputes (hard evidence of delivery), enables item-level ROI (know which items wear out fastest, replace smarter), reduces theft/shrinkage ($800/mo lost linens → $50/mo system leakage = $9k/yr recovered).

2. Pickup/Delivery Route Optimisation — GPS-Driven Sequencing, Multi-Stop Consolidation, Live Driver Tracking, ETA Accuracy

Custom system: [Route Optimizer]. Jessica's current routes (3 vans, 40 clients, 60 pickups/week): Van 1 visits 8 hotels in Fortitude Valley → Southbank → West End (2 hrs driving, 4 hrs billable time including load/unload). Van 2 visits 12 hotels in Kangaroo Point → New Farm → Bowen Hills (1.5 hrs driving, 4.5 hrs billable). Van 3 visits 20 hotels across South Brisbane + Woolloongabba (2.5 hrs driving, 5 hrs billable). Total: 13 hours driving/week across 3 vans. Route Optimizer ingests: 40 client GPS coordinates (hotel addresses), client pickup schedule (Mon/Wed, Tue/Thu, daily, custom), load capacity per van (500 items per van = ~200kg, space limit per run), time windows (Hotel A "pickup between 6–10am, not later"). System optimises: "Current route inefficiency: Van 1 drives Fortitude Valley (west) → West End (south) → Southbank (north) — triangular path, backtracking. Optimised route: Southbank (closest to depot) → Fortitude Valley (north-east) → West End (south-west) — linear path, 18 mins saved. Recommendation: Resequence 3 stops, reduce drive time 45 mins/Mon/Wed = 2.5 hrs/week × 52 weeks = $650 labour saved (1 driver 1.5 hrs/week × $52/hr × 50 weeks)." Jessica approves resequence. Next Monday, system generates optimised route for driver 1: "Route 2024-06-10 Van 1: 6:00am Southbank Grand Hotel (15 items), 6:25am Museum Motel (8 items), 6:50am Fortitude Valley Hilton (22 items), 7:30am West End Hostel (12 items). Total 57 items, drive time 45 mins, load/unload 1.5 hrs, return depot 8:45am." Driver follows GPS, system tracks live: "Driver 1 at Museum Motel, 6:27am (2 mins late, still on time window). System recalculates: arrival at next stop 6:52am (1 min buffer). ETA depot 8:50am." By month end: Van 1 saves 3.75 hrs/week × 4 weeks = 15 hrs/month × $52/hr = $780/month. Annualised: $9.36k labour savings from route optimisation alone. Plus: fuel savings (18 mins/week per van × 3 vans × 52 weeks × $0.25/km fuel @ 10 km/min = 1.8 hrs × 3 vans × 10 km/hr = 54 km/week saved × 52 = 2.8k km/yr × $0.25 = $700/yr fuel). Plus: driver stress reduction (no more guessing best route, GPS always optimal). Plus: client satisfaction (hotels get precise ETA, not "sometime between 6–10am").

3. Recurring Contracts + Auto-Billing — Schedule Pickup Days, Invoice Per-Service, Track Contract Terms, Proactive Renewal

Custom system: [Contract Manager]. Jessica sets up contracts: "Hotel A: Monday + Wednesday pickup/delivery, 40 linens per pickup (est.), $180/pickup. Hotel B: Daily pickup, 100 linens/day, $350/day. Hospital C: Mon/Wed/Fri, 300 linens/pickup, medical-grade cleaning surcharge +$50/service, 24-month contract expires 31 Dec 2026. Contract auto-renews unless either party opts out by 30 Nov." System auto-bills: every Monday 6am, after driver confirms pickup completion and hotel manager signs off, system auto-generates invoice: "Hotel A: 1-week service (Mon pickup + Wed delivery, Wed pickup + [pending] Fri delivery) = 2 services × $180 = $360. Invoice sent to hotel portal same day." Hotel A pays via Stripe (card, bank transfer) same day, system records. Month-end: "Hotel A: 8 services completed, all billable, 8 invoices issued $1.44k, 8 payments received (100% collection). Hospital C: 12 services (Mon/Wed/Fri × 4 weeks), 12 × ($350 + $50 medical surcharge) = $4.8k, all paid." System tracks: "Hospital C contract expires 31 Dec 2026, 201 days remaining. Renewal date: 1 Nov 2026 (60 days before expiry, send renewal proposal). Current contract terms: $350/day + $50 surcharge. Inflation applied: CPI +3% = new proposed rate $360.50/day + $51.50 surcharge. Jessica approves rates. System auto-emails Hospital C on 1 Nov: 'Your contract renews 1 Jan 2027. Proposed new terms: $360.50/day + $51.50 surcharge. Reply to confirm or we'll discontinue service effective 31 Dec 2026.'" Hospital C confirms. Renewal processed. Contract remains unbroken, no gap in service. Value: contract automation eliminates manual invoicing (Jessica currently spends 4 hrs/week calculating per-hotel services, tracking payments, chasing unpaid invoices). System reduces to 15 mins oversight. Per-week labour savings: 3.75 hrs × $52 = $195/week × 50 weeks = $9.75k/yr. Plus: zero late payments (auto-reminders sent, payment tracked, late-pay alerts triggered). Plus: contract renewals never lapse (system proactively nudges, ensures continuity, no surprise service cancellations).

4. Photo Proof + Damage Documentation — Timestamped Photos at Pickup/Delivery, Wear Assessment, Insurance Claims, Dispute Resolution

Custom system: [Photo Vault]. Monday 6:15am: driver 1 arrives Hotel A. Jessica (or driver via mobile app) takes timestamped photo of soiled linens pile (before loading). Photo metadata: GPS location "Hotel A Level 3", timestamp "2024-06-10 06:15", user "driver1", load ID "Van1-MON-001". System stores photo, compresses for storage. Hotel A manager Jessica takes second photo (hotel's perspective, for their records) — both photos archived. Driver loads 40 items into van. Before departure, driver 2 takes photo: "Van 1 loaded, 40 items, clean linens ready for delivery." System shows: time-lapse 3 photos (pile at hotel, loaded van, en-route). Driver 1 arrives laundry facility. Coordinator takes unload photo: "Van 1 unloading at facility, 6:35am, soiled linens ready for wash." System compares to hotel pickup photo (quantitative check: pile size seems consistent, no obvious shrinkage). If obvious difference flagged (e.g., hotel says "50 linens" but photo shows 20), system alerts Jessica: "Discrepancy: Hotel A claims 50 items, photographic evidence suggests ~25 items. Recommend contact hotel to verify." After wash, before delivery, coordinator takes photo: "Clean linens from Hotel A batch, post-wash 8:15am, sorted into delivery bin." Photo shows condition (no visible damage, items look clean). Wednesday 8:05am: driver 1 loads delivery bin for Hotel A, takes photo of clean linens (pre-delivery). Arrives Hotel A 8:30am. Hotel A manager takes delivery photo: "Clean linens arrived, 40 items, condition good." System compares photos: pre-delivery vs post-delivery (should match). If Hotel A later claims "Delivered linens were torn", system pulls photos: photo 1 (clean linens pre-delivery, no tears visible) vs photo 2 (linens at hotel, same condition). Hard evidence. Hotel A can't claim damage if photos show pre-delivery condition. Damaged item claims: every 2 weeks, coordinator reviews linens rejected by washing (torn seams, stains won't come out, holes). Coordinator takes close-up photo of damage, assigns damage code (seam-tear, stain-permanent, hole, colour-fade). System logs: "QR-HTLA-BS-00847, damage code 'hole-burn', photo date 2024-06-12, damage assessment 'customer damage (cigarette burn, not laundry fault)'." System tracks: "Hotel A: Jun damage count: 3 items (2 customer damage, 1 laundry fault). Cost: 2 × $85 = $170 (hotel responsible, not invoiced). 1 × $85 = $85 (laundry responsible, credited to next invoice)." Insurance claim (for items lost/damaged beyond normal wear): system generates claim report with photos, damage timeline, cost justification. Example: "Lost items (theft/shrinkage): 5 items × $85 = $425. Photo evidence: [timestamped photos of unload, pre-wash, post-wash, item not in delivery bin, item not in storage]. Timeline: [timestamps prove item was in system, last seen at point X, never made it to point Y]. Claim amount: $425." Value: photo documentation eliminates "he-said-she-said" disputes (photo is evidence), enables insurance claims (documentation is proof of loss), reduces false damage claims (hotels can't claim damage if photos show pre-delivery condition), protects laundry from liability (hard evidence of condition at each stage).

5. Billing Automation + Revenue Recovery — Service Tiering, Damage Cost Allocation, Lost-Item Charges, Recurring Invoices, Payment Reconciliation

Custom system: [Revenue Manager]. Jessica sets up service tiers: "Standard service: $180/pickup (regular linens). Medical surcharge: +$50 (hospital surgical linens, sterile processing, specialty washing). Oversized items: +$20 per item (jumbo bedding, curtains). Damaged beyond recovery: customer pays cost (Hotel A damages 2 sheets @ $85 ea = $170). Lost items: customer pays cost + 15% restocking fee ($85 + $12.75 = $97.75 per item, insurance covers above $500/month)." Hotel A weekly cycle: Monday pickup ($180) + Wednesday delivery ($180, auto-grouped with next Monday = $360/week). Medical Hospital C daily pickup ($350 + $50 surcharge = $400/day) × 6 days/week (closed Sunday) = $2.4k/week. System auto-bills after service completion (driver confirms pickup, coordinator confirms delivery, system auto-generates invoice): "Hotel A: week of 10 Jun, 2 services × $180 = $360. Damages: 1 item (laundry fault, -$85 credit). Adjustment: +$0 (no lost items). Net: $275. Invoice sent 11 Jun, due 18 Jun (7 days)." Hotel A doesn't pay by 18 Jun (no reminder sent yet, old system). Custom system: 19 Jun reminder sent "Invoice $275 due 18 Jun, please pay by 20 Jun to avoid late fee ($15)." Hotel A pays 20 Jun, late fee applied, system records. Month-end: "Hotel A total: 8 weeks × $360 = $2.88k services + damages -$170 (4 items laundry fault, credited) + lost items $0 + late fees $60 (paid late 3 of 4 weeks) = $2.77k revenue. Payment status: 3 of 4 invoices paid on-time, 1 paid late, 0 outstanding." System also tracks: "Lost items claimed by Hotel A: 2 items @ $97.75 = $195.50 (month-end). Claimed via portal, photo evidence attached. System routes to insurance (premium covers losses above $500/mo, Hotel A below threshold, Hotel A pays full $195.50). Invoice updated: +$195.50. New total: $2.97k." Hospital C: daily billing auto-reconciles against daily pickups. "Hospital C June: 23 weekdays × $400 = $9.2k. Payment: 23 payments received same-day (auto-payment via Stripe). Revenue confirmed." Year-end revenue: 40 clients × avg $2k/mo = $80k/mo × 12 = $960k annual. Current system: Jessica manually invoices (5 hrs/week × 50 weeks = 250 hrs/yr @ $52/hr = $13k labour). Plus: payment chasing (3 hrs/week × 50 weeks = 150 hrs @ $52/hr = $7.8k labour). Plus: billing disputes (2 hrs/week × 50 weeks = 100 hrs @ $52/hr = $5.2k labour). Total manual cost: $26k/yr. Custom system: 30 mins/week oversight (payment exceptions, damage disputes, new clients) = 26 hrs/yr @ $52/hr = $1.35k labour. Savings: $26k - $1.35k = $24.65k/yr labour. Plus: 99% collection rate (custom system prevents late payment via reminders, auto-payment setup, no manual friction) vs 92% current (some clients pay late, some never pay, Jessica gives up) = 7% additional revenue = $60k × 0.07 = $4.2k recovered. Total billing value: $24.65k labour + $4.2k collection = $28.85k/yr.

6. Linen Lost-Item Recovery + Stock Management — Item-Level Inventory, Wear Tracking, Retirement Forecasting, Reorder Automation

Custom system: [Inventory Manager]. Jessica starts with 4,000 linen items across 40 hotels: 2,000 bed sheets (various sizes: queen, double, single), 1,200 towels (bath, hand, face), 600 uniforms (chef, housekeeping), 200 surgical linens (hospital-grade). System tracks every item: "QR-HTLA-BS-00847 (Hotel A bed sheet): 506 washes completed, 500 expected lifespan, RETIRED (recommend replace). Cost new: $85. Wear cost/wash: $85 / 500 = $0.17/wash. Replacement: order Queen sheet $82 new. Cost to retire and replace: $82 (new) - $5 (scrap value) = $77 net cost. Current sheet condition: OK for guest use but near end. Action: retire this wash cycle, order 1 replacement sheet this week." System auto-generates: "Weekly retirement forecast: 12 items approaching end-of-life (500+ washes done). Recommend replacement order: 8 queen sheets @ $82 ea = $656, 2 bath towel sets @ $45 ea = $90, 2 surgical linens @ $120 ea = $240. Total: $986 this week. Budget remaining FY: $15k (for 52 weeks = $288/week avg). This week $986 is above average, push $300 to next 3 weeks." Jessica approves plan. System places order to supplier (integrated with Linen King supplier API). Items arrive Wed, barcode-labelled by supplier (or Jessica labels in-house), scanned into system: "12 new items added to inventory. System now tracks: QR-HTLA-BS-00851 (new queen sheet, 0 washes, 500 expected lifespan, assigned to Hotel A)." Old items (12 near end-of-life) marked as retired, removed from active pool. System forecasts: "Retirement pace: 12 items/week (avg). Annual retirement: ~600 items. Replacement cost: 600 × avg $80 = $48k/yr. Allocation: 40 hotels, avg 100 items/hotel. Each hotel replaces ~15 items/yr @ $1.2k/yr replacement cost (budgeted)." Lost items during the year: system tracks where items disappear. "Jan–Jun 2026: 4,000 items total. Retirements: 120 items. Lost items: 15 items (0.375% loss rate). Lost by hotel: Hotel C 8 items (theft? staff steals? mixed in other hotel's delivery?). Recommendation: investigate Hotel C. Possible causes: (1) delivery count inaccurate (coordinator didn't scan all items during delivery), (2) theft on hotel staff side, (3) mixed in another hotel's delivery." Jessica calls Hotel C manager: "Jun data shows 8 items from your hotel in our system (scanned at pickup) but never arrived at your delivery (not in delivery scan). Possible scenarios: items lost in-transit, mixed in another hotel's bin, or mislabelled. Photo evidence: [photos of pickup, unload, delivery]. Can you check your linen storage for items not marked as yours?" Hotel C checks, finds 3 items from Hotel D mixed in their closet (driver error, same colour towels). System updates: "3 items reassigned to Hotel D, found at Hotel C." Lost items now 12 (down from 15, mystery solved). Remaining 12 truly lost: 8 from Hotel C (high loss, investigate further) + 4 from other hotels (normal shrinkage 0.1%). System alerts Jessica: "Hotel C loss rate 0.8% (vs avg 0.1%). Recommend: (1) recount linen stock with Hotel C manager (audit), (2) install camera in Hotel C linen room (if high-value items), (3) consider requiring linen logs (staff sign-out linens, sign-in returns)." Value: inventory management prevents losing track of stock (every item tracked, loss visibility), optimises replacement (retire before failure, buy smarter), recovers mixed shipments (photo + barcode catch errors), enables theft investigation (data proves theft, enables corrective action). ROI: reduced shrinkage from 1.5% (600 items lost/yr) to 0.2% (80 items lost/yr) = 520 items saved × $80 ea = $41.6k/yr value recovery. Plus: inventory forecasting reduces emergency orders (no more "we're out of sheets, buy at premium") = 5% supply cost savings on $48k/yr replacement = $2.4k/yr supply savings. Total inventory value: $41.6k + $2.4k = $44k/yr.

Commercial Laundry ROI: 3-Van Operation, 40 Hotels, 18-Month Payback

Build cost: $48k (barcode tracking + route optimisation + recurring billing + photo vault + inventory management + mobile driver app). Year 1 ops: $6k/yr (hosting, barcode label supplier integration, Stripe fees, mobile app updates). Total Year 1 investment: $54k. Value captured: (1) Route optimisation: 3 vans × 3.75 hrs/week saved × $52/hr × 50 weeks = $29.25k/yr labour saved (can deploy savings to: add 4th van for growth, or reduce headcount 0.5 FTE). (2) Billing automation: eliminate 250 hrs manual invoicing @ $52/hr = $13k/yr, plus 150 hrs payment chasing @ $52/hr = $7.8k/yr, plus 100 hrs dispute resolution @ $52/hr = $5.2k/yr. Total billing labour: $26k/yr. (3) Payment recovery: 99% collection (custom system) vs 92% (current) × $960k annual revenue = 7% additional revenue = $67.2k recovered (Year 1 partial, assume ramp to full by Q2 = $35k Year 1). (4) Inventory shrinkage: reduce loss from 1.5% to 0.2% × $960k revenue (proxy for inventory replacement) = $41.6k/yr value recovered. (5) Supply cost savings: 5% reduction on $48k/yr replacement orders = $2.4k/yr. Year 1 total value: $29.25k (labour) + $26k (billing) + $35k (payment recovery, ramp) + $41.6k (shrinkage) + $2.4k (supply) = $134.25k. Year 1 net: $134.25k - $54k = $80.25k value. Year 2: repeat value ($134.25k) minus build cost = $128.25k profit. Break-even: 5 months. Conservative upside: firm adds 2nd location (Melbourne, 40 more hotels), platform scales zero build cost, Year 2+ profit $200k+/yr. Want to model ROI for your laundry operation? Check platform pricing or book a call—we'll handle barcode tracking, route optimisation, recurring contracts, photo documentation, damage assessment, lost-item recovery, and billing automation.

Six FAQs

What's the difference between laundry service software and general inventory management systems?

General inventory (e.g., Shopify, ERPNext): designed for retail stock (products you buy, sell, or warehouse). Laundry-specific software: designed for cyclical service (items you own, rent out, clean, return). Key differences: Inventory tracks "how many shirts in stock?". Laundry tracks "which sheets are at which hotel, which are being cleaned, when do they return?" Inventory assumes items are fungible (one shirt same as another). Laundry tracks wear per item (sheet A has 450 washes left, sheet B has 300 left, retire B first). Inventory for point-of-sale. Laundry for service delivery (pickup/dropoff). Inventory billing: per-unit sold. Laundry billing: per-service (recurring weekly, monthly contracts). General inventory doesn't track damage/wear. Laundry critical tracks per-item wear, retirement forecasting, lost-item recovery. Verdict: general inventory systems aren't designed for laundry (can't track item-level wear, can't handle recurring contracts, can't manage pickup/delivery routes). Custom laundry system is purpose-built.

How does barcode tracking work with thousands of linens from multiple hotels?

Every physical linen item gets a unique barcode (QR code or barcode label, thermal-printed, waterproof, survives 500+ wash cycles). Hotel A sheets get barcodes like QR-HTLA-BS-00847, QR-HTLA-BS-00848. Hospital C surgical linens get QR-HSPTC-SL-00012. System ingests barcode via mobile app (driver scans with phone camera or barcode scanner gun). Scan workflow: driver arrives Hotel A, opens mobile app, selects "Hotel A pickup", taps "Scan items", camera activates. Driver points at first sheet's barcode, app reads QR code, system logs: "QR-HTLA-BS-00847 scanned at Hotel A, 6:15am, GPS confirmed." Driver scans all 40 items (5 mins, vs manually counting 15 mins). System shows: "40 items scanned, all match Hotel A's current inventory. Load complete." If driver scans an item not expected (e.g., QR-OTHER-TW-00043 from Hotel B mixed in), system flags: "QR-OTHER-TW-00043 detected, not from Hotel A. Remove from load or reassign to Hotel B." Prevents mixed shipments. At facility, coordinator scans entire batch into warehouse: "Van 1 load 40 items received, all 40 barcodes confirmed against load manifest." System matches: scan list = manifest, 100% accuracy. If 1 item missing, system flags immediately (vs manual count where 39/40 looks "about right"). After wash, items sorted into delivery bins per hotel, coordinator scans items into bins. System confirms: "Hotel A clean delivery bin: 40 items scanned, matches pickup (40 items, same barcodes)." Missing item detected instantly: "QR-HTLA-BS-00850 expected but not scanned. System searches: last known at facility 8am Wed, not in any delivery bin. Action: item lost in-transit or facility." Search begins. Barcode tracking turns hours of manual searching into milliseconds of system lookup.

Can the system integrate with hotel linen management systems (like Linen King, Ecolab)?

Partially. Linen King (major AU supplier for hotels/hospitals): provides linen rental + supply service (hotels don't own sheets, they rent from Linen King, Linen King laundries them). Custom laundry system integrates differently: if the laundry IS Linen King (rents to hotels, does own laundry), system tracks full cycle. If the laundry is independent (contracts with hotels, doesn't handle other vendors), system can import hotel linen manifests (if hotel provides CSV of linens they own). Example: Hotel A owns 500 sheets (purchased from supplier, tracked in Hotel A's own system). Laundry picks up, cleans, returns. Laundry system tracks: "40 of Hotel A's 500 sheets in our facility this week, due back 12 Jun." If Hotel A also rents 200 sheets from Linen King (separate vendor), those aren't in laundry system (they're Linen King's, Linen King manages them). Custom system integrates with: (1) supplier APIs (if laundry buys blanks from supplier, auto-order when inventory low). (2) Hotel property management systems (Opera by Oracle, if hotel provides API, laundry can auto-pull linen requirements per room-night). (3) Accounting software (QuickBooks, Xero, if laundry needs cost sync). (4) Payment processors (Stripe, BACS for AU). Current limitation: system assumes laundry owns/manages linens. If linens are owned by vendor, coordination requires manual handoff. Future: system could integrate with Linen King API (if LK opens it) to sync rental inventory.

How does the system handle medical-grade or sterile laundry workflows?

Hospital surgical linens require sterile processing (higher temperature, longer cycle, separate washing facilities, zero cross-contamination). Custom system tracks: "Hospital C surgical linens (QR-HSPTC-SL-00012 etc.): 200 items total. Dedicated wash cycle: Monday/Wednesday/Friday only, 90°C sterile wash, separate facility, staff certified in sterile handling, post-wash sterile packaging." System flags: "Surgical batch delivery (Hospital C): items must remain in sterile packaging from wash to delivery. Driver must: (1) maintain temperature-controlled van (if longer than 2 hours). (2) deliver directly to Hospital C sterile storage (not left in general linen room). (3) get signature from sterile processing nurse (not just front desk)." Billing surcharge: +$50/service (covers labour, compliance, segregated facilities). System tracks compliance: "Hospital C surgical deliveries Jun: 12 deliveries, 12 confirmed by sterile processing staff, 0 breaches. Audit trail: [timestamp, staff signature, temperature log if applicable]." If breach (driver leaves sterile linens in non-sterile linen room), system flags: "Breach: delivery 12 Jun, left in general linen room (not sterile storage). Hospital C has 4 hours to validate sterility (labs can test). If validation fails, items must be re-washed (cost: $50 emergency service charge, hospital pays or laundry absorbs)." System tracks: "Jun breaches: 0. Compliance: 100%." For accreditation (hospitals require ISO 13485 or equivalent certification for linen service), custom system generates: "Audit report: [all deliveries, staff training dates, equipment maintenance logs, sterile validations]. Proof of compliance." Medical-grade adds complexity but system handles it via (1) segregated workflows, (2) compliance tracking, (3) staff certification logs, (4) breach alerts.

What about staffing peaks? Do drivers work 5 days or 6 days per week?

Staffing depends on contract volume. Example: 40 hotels, pickup patterns: 20 hotels Mon/Wed (2 pickups/week), 15 hotels Tue/Thu (2 pickups/week), 5 hotels daily (6 pickups/week). Calculation: (20 × 2) + (15 × 2) + (5 × 6) = 40 + 30 + 30 = 100 pickups/week. Capacity per van: 3 pickups/run @ 2 runs/day (morning 6–10am, afternoon 12–4pm) = 6 pickups/van/day. 3 vans × 6 = 18 pickups/day. Per week (5 days): 18 × 5 = 90 pickups. Current: 100 pickups, need 18 pickups overflow = 1 extra van (part-time, 2–3 days/week). Custom system forecasts: "Weekly pickup demand: 100 pickups. Capacity: 3 vans (90), 1 van (10). Request: allocate 3 full-time drivers + 1 part-time (Tue, Wed, Thu). Cost: $80k/yr (3 × $85k/yr salary + 1 × $25k/yr part-time)." Peak weeks (post-conference season, many hotels booked): system predicts "Week of 2 Jul, conference in Brisbane, hotels at 95% occupancy, forecast 120 pickups (20 pickups above avg). Recommendation: overtime (3rd driver works 6 days Tue–Sun) or rent 4th van short-term." System tracks actuals: "Week 2 Jul, actual pickups 118, 4th van deployed (Tue–Fri), cost $800 rental. Managed peak without over-hire." Staffing optimization saves: 1 full-time driver salary ($85k/yr) if routes optimised (current 3 vans running inefficient = need 3.5 drivers, custom system = 3 drivers + part-time overflow). Savings: 0.5 FTE @ $85k = $42.5k/yr. System factors this into ROI.

How does the system handle customer disputes over missing or damaged linens?

Dispute workflow: Hotel A claims "We're missing 5 sheets from last week's delivery." System retrieves: (1) pickup photos (Hotel A soiled linens before loading), (2) unload photos (at facility), (3) post-wash photos (clean linens ready for delivery), (4) delivery photos (clean linens at Hotel A). Barcode scan history: "5 sheets scanned at Hotel A pickup on 10 Jun, scanned into facility 6:35am same day, washed 6:45–8:15am, scanned into Hotel A delivery bin 8:15am, scanned at Hotel A delivery 12 Jun 8:30am." Photos show: sheet 1, 2, 3, 4, 5 all present in delivery bin, all present in delivery photo at hotel. Evidence: sheets were delivered. Hotel A manager checks again, finds 5 sheets in closet (they misplaced them, not missing). Dispute resolved: no charge, relationship intact. Alternative scenario: Hotel A claims "Sheets delivered are damaged (torn)." System retrieves delivery photos: sheets show no visible damage at delivery. If Hotel A insists damage is present, system offers: (1) send photo of damaged sheet to laundry (Hotel A takes photo), (2) laundry assesses damage (laundry fault vs customer damage, e.g., burn mark = customer damage, seam-tear from laundry = laundry fault). (3) if laundry fault confirmed, credit issued (cost of damaged sheet refunded or replaced free). If customer damage confirmed, Hotel A pays ($85 cost). Photo + barcode evidence prevents he-said-she-said disputes (hard evidence of condition at each touchpoint). System also tracks: repeat damages per hotel (Hotel C damages 8 items/month vs avg 1 item/month), alerts laundry "Hotel C's damage rate is high. Possible causes: (1) laundry over-washing (too hot, too long, damages items). (2) customer handling (staff wrings linens too hard, leaves on radiator, causes damage)." Laundry investigates: reduce wash temperature for Hotel C, damage count drops to 2 items next month. Root cause found and fixed.