▤LAYER 01 / CATALOG
Product and package record
The catalog is the source of the SKU name, color, images, price and package description used throughout the journey. It should also identify the approved package revision and the fulfillment method for each offer. These records connect the chair marketed on the screen with the unit that can actually be supplied.
Assign responsibility for catalog changes. Before a new item becomes available, confirm that its physical sample, product copy, images and position mapping have passed the agreed release process.
▯LAYER 02 / EXPERIENCE
Customer selection interface
The selection interface turns the product record into a readable shopping path. It needs a clear current selection, visible availability and a confirmation screen that matches the purchase. The portrait format shown in the references offers a suitable area for product thumbnails and concise model details.
Confirm language support, touch behavior, inactivity handling and recovery screens in a working demonstration. Interface illustrations in the reference images do not prove the capabilities or usability of the delivered software.
▰LAYER 03 / TRANSACTION
Order and payment coordination
The transaction layer associates the order with the payment attempt and the permitted fulfillment action. It needs a defined response to success, cancellation, timeout and duplicate input. The exact design may depend on the terminal, network connection and regional payment provider.
Use one traceable order reference across the application and payment records where the contracted integration supports it. Agree how the system prevents an interrupted session from creating an unclear charge or an unintended second collection.
◫LAYER 04 / FULFILLMENT
Physical collection control
This layer connects an accepted order to the approved physical route. In a locker version it could involve an addressed lock and defined door state; in an order kiosk it could involve a pickup reference and staff handoff. The selected route must be confirmed in the project scope.
Review the mechanism with production-equivalent hardware. A windowed front alone does not establish automatic door release, package detection, anti-pinch behavior or any specific sensor arrangement.
▦LAYER 05 / RECONCILIATION
Stock and outcome records
Stock records should reflect what the system actually knows about a position and its merchandise. Depending on the supplied sensors and software, the system may observe only a command, a door event or an operator confirmation. Those observations are not interchangeable with proof that a chair pack was collected.
Define when a unit becomes unavailable, when its outcome is final and when a physical check is required. Use a reconciliation process that can separate available, allocated, uncertain and out-of-service positions if the system supports those states.
◎LAYER 06 / OPERATIONS
Operator access and service
The operating layer covers authorized replenishment, issue review, content updates and service access. Decide which tasks happen at the machine and which can be completed through any included management platform. Access should reflect each role, from stock refiller to technical service provider.
Remote dashboards, APIs, alerts and export functions are configuration items. Ask for their actual scope, account model and support ownership rather than treating them as automatic features of the pictured machine.
