▤LAYER 01 / CATALOG
Product identity and package approval
The product record links the customer-facing offer to a specific litter formula, pack quantity and approved package revision. It should contain the data needed by the menu and the operator’s stock plan. A reliable catalog prevents similar-looking bags from becoming interchangeable in the live system.
Assign ownership of changes to descriptions, prices and package images. Before a revised product becomes available, confirm that its physical package still fits the permitted positions and delivery route. Keep a controlled record of approved variants and their operating restrictions.
▯LAYER 02 / EXPERIENCE
Selection and availability display
The customer interface translates the catalog into a manageable shopping path. It needs a readable selection, a current availability state and a confirmation view that reflects the intended purchase. The central portrait screen shown in the references is the natural location for that interaction.
Confirm the supported input method, languages, accessibility options and timeout behavior in the actual software. Screen artwork is useful for layout direction but does not establish live functionality, payment integration or the quality of recovery messages.
▰LAYER 03 / TRANSACTION
Order and payment coordination
This layer associates the selected unit with the payment attempt and the permitted fulfillment action. It should handle accepted, declined, cancelled and uncertain responses according to the configured provider. A clear transaction reference helps connect the customer’s report with the records used for resolution.
Review duplicate input, network interruption and application restart behavior. Agree whether an order can be retried and under what conditions. The final behavior should prevent an unclear session from creating an unintended second charge or an unsupported duplicate delivery.
→LAYER 04 / DELIVERY
Bay assignment and physical transfer
The fulfillment layer maps the order to the correct cabinet, stocked position and approved delivery route. It coordinates the mechanism and any supplied feedback so the application can direct the customer to the appropriate lower opening. This mapping is especially important with two similar display bays.
Confirm how the controller identifies left and right positions and how an unavailable lane is isolated. Test the actual mechanism and package combination. The exterior references do not reveal the motor, elevator, sensor or transfer technology used inside the cabinets.
▦LAYER 05 / RECONCILIATION
Stock states and delivery outcomes
The stock record should reflect the evidence that the configured system can actually obtain. Depending on the installed hardware, that may include a vend command, an item-passage event, a pickup-door event or operator confirmation. These observations should not be treated as identical proof of successful collection.
Define the states for available, allocated, uncertain and out-of-service stock where supported. Review unresolved events before returning the affected position to sale. A physical reconciliation process is needed wherever the software cannot establish the outcome with sufficient confidence.
◎LAYER 06 / OPERATIONS
Operator tools and service ownership
The operating layer covers authorized replenishment, stock corrections, issue review and maintenance access. Decide which tasks are performed locally and which are available through any included management platform. Assign responsibilities to the site operator, payment provider and machine service team.
Remote alerts, dashboards, APIs and automatic stock updates are scope items to confirm. Obtain a demonstration of the proposed tools and their account permissions. A dual-cabinet design does not by itself imply remote management, cloud connectivity or a particular reporting service.
