What the current Spaze Storage application supports
Explore booking, retail, payments, stock, pricing, hardware, and operator tools in the reviewed implementation.
Before you begin
- Confirm the installed application and commit before applying these instructions.
- Identify whether the site needs booking storage, retail vending, employee storage, delivery handoff, or the proposed EV charger borrowing journey.
- Record the intended project, service, device, resources, and physical controller.
Verified against integrate-nekospaze-app at 5d1abe32660e on 8 September 2026. Capabilities are source-verified; deployment and hardware operation were not tested in this review.
Step by step
Choose the operating flow
The kiosk has parcel and retail modes. Parcel provides the six-digit booking-code handoff. Retail provides shopping, pickup, and restock screens. Selecting a flow changes the available routes; it does not add an employee or rider authorization policy.
Connect a real booking
Spaze App selects a locker service and resource, creates an order, and displays booking codes and progress. The kiosk mirrors booking and resource data, checks its mapped resources and booking period, and sends a local serial command for the selected action.
Commission the physical installation
Setup and Settings provide serial discovery, device binding, controller command tools, and reader diagnostics. Verify each compartment-to-command mapping on the actual installation. A detected reader or accepted command is not proof of an authorized person or a completed physical handoff.
Choose a policy the implementation can enforce
The current parcel flow grants access to the holder of a valid booking code. Owner-only employee storage, one-use rider deposit, recipient personal authentication, staff-gated maintenance, and face-verified charger borrowing and return require implementation. Use the corresponding solution articles to define and test those requirements.
You’re ready when
You can distinguish working application paths, configuration options, and policy work that must be completed before launch.
Troubleshooting
- A feature is listed in setup but does not work in the user flow
- Trace whether it is only a stored setting, a hardware test, or an actual access decision. The authentication article identifies the current gaps.
- Someone describes the installation as fully offline
- Verify the existing local data, device commands, booking event synchronization, and revocation behavior during disconnection. The source has local mirrors and a queued update path; it does not establish unrestricted offline operation.
- Food or occupancy labels are treated as sensor readings
- Food is a booking category, and booking occupancy is a recorded timestamp. Confirm physical hardware and sensors separately; these labels do not establish temperature control or real-time physical occupancy.
Technical details
- Spaze App
- Provides locker selection, checkout, booking detail, map navigation, labelled codes, and booking history in the reviewed application.
- Parcel kiosk
- Matches booking codes locally, opens mapped resources through Serial capabilities, then queues occupancy or completion updates.
- Retail shopping
- Browse stocked compartments, add or remove compartments from the cart, review totals, and submit a retail order. Each selected compartment produces one product line; the cart is not a freely adjustable quantity order.
- Retail promotions
- Apply an eligible promo code at checkout. The kiosk checks product applicability, minimum spend, expiry, and remaining uses, and calculates fixed or percentage discounts from the configured offer.
- Payments and retail pickup
- Choose PromptPay, Credit Card, TrueMoney, or AliPay and complete the displayed payment flow. After the server reports payment completion, the kiosk proceeds to the selected compartments. This is not a verified physical card-terminal integration, and the pickup screen does not reliably surface returned door-opening failures.
- Vendor and product catalog
- Console provides vendor and product create, edit, and delete tools, including vendor colour, product SKU, description, price, media, and visibility. The kiosk renders the product image URL; Console's icon alternative is not used as a kiosk product image.
- Retail stock and restocking
- Stock links a product to a compartment. A paid retail product line reduces that compartment's stock by one. Restock opens a compartment and assigns quantity one of its existing product; it has no product picker or quantity editor. Entry has no staff credential challenge.
- Duration and price schedules
- Console can define named duration/price schedules and assign resource pricing. Retail product prices are managed separately. Do not assume that every configured schedule is an hourly rate.
- Booking extension
- The booking owner can choose an eligible longer duration in Spaze App and pay the additional charge. The server rejects completed bookings, missing service pricing, non-positive added charges, and overlapping reservations. Successful extension payment increases the booking end time.
- Console deposits and mailbox commands
- Console provides immediate, undated deposit reservations with owner and participant selection, plus mailbox Open, Activate, Inactivate, and Notify/Use requests. These HTTP-based tools are a different integration path from the kiosk's shared database bookings.
- Notifications
- Console exposes a mailbox Notify/Use request with an optional attachment. This source review does not establish automatic booking SMS, email, or push delivery; confirm the installation's notification integration separately.
- Setup and hardware diagnostics
- Connect, Discover, Config, and Review save the local setup. Native tools list serial ports, scan controller boards, test commands, and capture supported reader scans. Apply does not provision cloud devices or access rules.
- Maintenance and data inspection
- Retail Restock can switch shared resources between Active and Maintenance. Settings inspects commands, resources, reservations, access rows, orders, stock, and pending events, and can resync local mirrors. Cloud permissions and physical command results need separate verification.
- Language and presentation
- The kiosk offers English and Thai. Retail vendor accents and product images come from catalog data; shell branding is bundled assets and CSS. The 100-second idle timeout is a source constant, with route and operation exceptions.
- Local data and queued updates
- Local mirrors support the implemented cached booking flow and queue occupancy/completion updates. Events are discarded after three failed sync attempts. Verify the server record; offline preferences and an empty queue do not establish successful reconciliation.
- Recorded state
- occupiedAt records the booking's occupancy transition; completedAt records completion. Neither timestamp proves an item is present or a door is closed.
- Personal and staff access
- Reader capture and authentication settings exist, but personal identity authorization and a staff credential gate are absent from the reviewed kiosk routes.
- EV charger borrowing — solution design
- Store an EV charger inside an assigned compartment. The booked person verifies their face to collect it and again to return it, keeping the same booking open until the correct item and closed door are confirmed. Face authorisation, equipment matching, and this borrowing lifecycle require integration; this is not a fixed charging-station service.
Common questions
- Can Console reservations automatically replace the app booking flow?
- The reviewed Console deposit component uses its reservation and IoT APIs, while the current kiosk uses mirrored database bookings and booking access rows. Verify the site's connection between those paths before relying on it.
- Does this page certify a deployed installation?
- No. It describes the inspected source. Device configuration, physical wiring, account permissions, and runtime behavior still need installation testing.
Still stuck? Tell support what happened and which step you reached.
Email support