WEIMI / DEPOT TO ROUTE
One logistics unit.
Several stock decisions.
Keep the arriving pallet connected to what happens next.
IDENTIFY → MATCH → RECEIVE → ALLOCATE
DEPOT RECORD 01
Introduction
A distribution depot receives a pallet of drinks and snack cases destined for several vending routes. The label scans correctly. The receiving screen shows one logistics reference, but the route team still needs to know which cases arrived, what was short and which products can be allocated to each cabinet. One readable pallet label has not settled those decisions.
The GS1 Logistic Label Guideline, displayed as release 1.3, ratified in July 2019 on the reviewed page, explains how a logistic unit is identified by a Serial Shipping Container Code, or SSCC. It describes linking physical movement to electronic business messages and gives separate treatment to homogeneous and heterogeneous units.
This brief translates that evidence into a replenishment purchase specification. Its subject is the unit-to-contents relationship at the depot and the record that remains after stock is split. It does not certify a warehouse system, determine a legal traceability requirement or promise that a WEIMI cabinet reads SSCC labels. The route and cabinet processes need their own demonstrated interfaces.
DEPOT RECORD 02
Quick Answer
The source describes SSCC as the mandatory element of a GS1 Logistic Label. That is a standards statement about that label, not a claim that every vending operation is legally required to implement electronic pallet receiving.
DEPOT RECORD 03
Comparison Table
| Record | Its job | Purchase question |
|---|---|---|
| SSCC | Identify the specific logistic unit | Who assigns it and how is it linked to the shipment? |
| Trade-item identifier | Identify the relevant product or packaging level | Are supplier and receiver item records aligned? |
| Despatch Advice / ASN | Communicate the shipment contents linked to the unit | Does the receiver process it before arrival? |
| Receipt exception | Document missing, damaged or disputed goods | Who checks, approves and notifies the supplier? |
| Route allocation | Associate accepted stock with its next operational destination | What relationship remains after cases are split? |
The route-allocation row is a proposed vending operating control, not a claim that the GS1 label stores every subsequent cabinet movement. Review the required detail with the warehouse and route-system owners.
DEPOT RECORD 04
Who Should Buy This
Use this review for depots receiving mixed replenishment pallets, distributors offering a warehouse connection alongside vending equipment, and operators outsourcing storage or repacking to a logistics provider. It is especially useful where one receiving unit supplies several routes and where a quoted inventory feature leaves the depot-to-cabinet handover unexplained.
Include the supplier dispatch team, warehouse-system owner, receiving supervisor and route planner. The equipment vendor should explain the cabinet-side stock process, but it may not control the supplier’s logistics labels or electronic messages. Identify that division of responsibility before ordering an integration.
A small operation with occasional deliveries may choose a documented manual relationship instead of an automated interface. That choice should follow actual workload and information needs. A larger fleet should still prove its data flow with a limited trial rather than assuming that a warehouse scanner creates complete cabinet traceability.
DEPOT RECORD 05
How We Evaluate Smart Vending Machines
The shortlist uses current WEIMI public product descriptions and the reviewed GS1 guideline. It is a procurement comparison of operating formats, not independent equipment testing. No public listing reviewed here establishes SSCC parsing, an ASN interface, a warehouse integration or automatic lot-level route allocation.
Our proposed acceptance begins before the cabinet. Use an agreed dummy shipment with a mixed contents record. The receiving demonstration should show the unit identifier, the related items and packaging levels, and the expected receipt quantities. Then include a missing-case or damage exception and show the approved correction rather than treating the dispatched quantity as unquestioned receipt.
Follow a portion of accepted stock into a route allocation and then the appropriate cabinet-loading process. Observe how the software or manual record connects the stages. If a provider claims an automated connection, ask for the actual interface, version and transaction output. If the handover is manual, document the operator action and verification.
Finally, test a unit whose expected message is unavailable and a repeated scan of a previously received unit. Those are project acceptance scenarios, not quoted GS1 test requirements. Agree how the application prevents an unexplained stock increase and who resolves the exception. One successful normal receipt is insufficient evidence for those cases.
DEPOT RECORD 06
Key Buying Factors
Define the logistic unit. GS1 describes an item of any composition established for transport or storage that needs management through the supply chain. A pallet can be a logistic unit, but the idea is not limited to pallets. Specify the unit supplied to your depot and the relationship to any cartons or other packaging contained within it.
Separate identity from contents. The guideline explains that cartons and cases can carry a GTIN barcode without being GS1 Logistic Labels when no SSCC is present. An item identifier and a unit identifier serve different jobs. Keep both in appropriate fields rather than putting whichever barcode was scanned into a generic product-code box.
Handle mixed pallets explicitly. The guide distinguishes heterogeneous units with different trade items at the highest packaging level. For a heterogeneous unit that is not itself a trade item, it says no GTIN and related trade-item information should be included on the logistics label, and strongly encourages electronic messaging linked with the SSCC. Do not present one content GTIN as a summary of a mixed load. Have the specialist review units that are themselves traded items separately.
Align the packaging level. The guide’s homogeneous example uses a case GTIN and a count of cases. Procurement should therefore ask how cases relate to the saleable packs used by the route team. A quantity of twelve cases is not automatically twelve retail units. Request the approved conversion and record ownership instead of inferring it from a delivery description.
Process the message before arrival. Section 9.5 recommends receiving and processing the Despatch Advice or ASN before the goods arrive. The guideline also identifies electronic communication, aligned item master data, readers and a warehouse system as prerequisites for its receiving process. Confirm the actual message route, timing, error visibility and responsible support party.
Agree checks and exceptions. GS1 states that the extent of inspection depends on the supplier-receiver agreement: the receiver may accept the unit based on the message or check contents and damage, particularly for multiple products. The contract should address deliveries without an ASN. Decide what happens operationally; do not invent a universal obligation to reject every unannounced delivery.
Preserve the relationship during handling. The guide recommends retaining labels until put-away is complete and preserving the SSCC relationship in storage where possible. It also gives examples of rebuilt pallets receiving new labels and retaining relationships between old and new consignments. Specify the evidence your logistics provider supplies when it splits, rebuilds or reallocates the received stock.
Distinguish a new carrier segment from a new unit. The guideline says an existing SSCC must not be changed when adding or replacing a label segment; its carrier-segment discussion preserves the original SSCC. That is different from creating a rebuilt logistics unit. Ask the qualified labeling owner to define the correct operation rather than replacing a number merely because a carrier or destination changes.
DEPOT RECORD 07
Best Smart Vending Machines
The suitable cabinet follows the goods and access method. Depot receiving is a separate system scope. The following public-list shortlist does not rank SSCC support or imply that any model includes a logistics label service.
DIRECT-ACCESS RETAIL
WEIMI Single-Door AI Vision Smart Fridge
The public listing describes packaged drinks and compatible snacks, camera-based checkout, direct selection, cloud management and product registration with recognition testing. Consider it where the intended assortment and shopping behaviour pass an actual demonstration.
The receiving SSCC does not replace SKU registration or the approved shelf arrangement. Request a demonstrated handover from accepted depot stock to the product records used by the fridge. No reviewed evidence proves pallet-code decoding or an automatic warehouse connection.
CHANNEL VENDING
WEIMI WM22 Touchscreen Snacks & Drinks Machine
The WM22 page describes a 21.5-inch touchscreen, cooling, inventory functions and adjustable dispensing-channel options. Consider it for a defined packaged assortment after testing the exact goods and delivery path.
Ask how route quantities become the approved channel loads. A completed pallet receipt cannot prove the right cases were picked or the right products loaded into each channel. The public listing does not establish SSCC receiving or a case-to-unit conversion interface.
WORKPLACE SUPPLIES
WEIMI PPE Employee-System Vending Machine
The listing describes staff-card access, role permissions, issue limits and downloadable reports. Consider it for controlled workplace supply issue with an approved policy owner and suitable pack-handling trials.
A supplier’s mixed logistics load might contain different supply packs, while the issue record follows the configured machine items. Request the relationship between receipt, restock and authorised issue. Staff-card access does not demonstrate logistics barcode reading, and the cabinet does not certify the protective goods.
DEPOT RECORD 08
Feature Comparison
| Operating boundary | AI fridge | WM22 | PPE system |
|---|---|---|---|
| Published customer or user flow | Direct selection with camera checkout | Touchscreen selection and configured delivery | Staff-authorised item issue |
| Cabinet acceptance | Actual-pack recognition and placement | Exact-pack delivery and loading | Permitted issue and pack handling |
| Depot-to-cabinet question | Accepted stock to registered SKU | Accepted stock to channel load | Accepted stock to configured supply item |
| SSCC / ASN support | Not established by public listing | Not established by public listing | Not established by public listing |
Ask for an interface demonstration only where the project needs it. A cloud stock feature is useful evidence of a listed function, but it is not proof of every upstream logistics process or data field.
DEPOT RECORD 09
Cost & ROI Analysis
This hypothetical calculation concerns receiving reconciliation labour only. Assume thirty replenishment units per month and a staff allowance of $30 per hour. Compare a manual process taking fifteen minutes per unit with a documented contents-message process taking seven minutes. These times are assumptions, not observed WEIMI results.
| Assumed measure | Manual reconciliation | Documented message process |
|---|---|---|
| Units per month | 30 | 30 |
| Time per unit | 15 minutes | 7 minutes |
| Total labour | 7.5 hours | 3.5 hours |
| Labour allowance | $225 | $105 |
The assumed monthly difference is $120. If a purely illustrative implementation allowance is $720, simple recovery of that allowance is six months, before recurring fees, labels, readers, support, exception work or training. It is not an equipment price or supplier integration quote.
For a less favourable case, assume the manual task takes twelve minutes and the message process takes ten. Thirty units then produce a one-hour difference, or $30 monthly at the same rate. Recovery of the same allowance becomes twenty-four months. Measure both normal and exceptional receipts; faster matching of an expected shipment can be offset by time spent resolving missing messages.
Quote warehouse work, any route-system connection and cabinet-side configuration separately. Avoid counting the same reduction in receiving labour again as a route-loading saving. No avoided loss, recall cost, sales increase or legal penalty is monetised in this example.
DEPOT RECORD 10
Best Choice by Scenario
Mixed drink and snack replenishment: choose the physical retail format after assortment trials. An AI fridge may suit browsing and multiple-item shopping; WM22 may suit product selection and channels. Both require an agreed receipt-to-route relationship where depot traceability is part of the project.
Workplace supplies arriving in combined loads: shortlist the PPE system if staff permissions and issue limits meet the approved programme. Keep the logistics-unit contents separate from the item and role records used for employee access. Determine the applicable goods and safety requirements with the responsible team.
A depot with an established warehouse platform: evaluate the supplier’s SSCC and contents-message interface against that platform. Then test the handover to route planning. Avoid building a new cabinet workflow around a field that the warehouse does not actually export.
An outsourced consolidator: ask for receipt, rebuilding and outgoing-unit relationship records. Define who assigns labels and who communicates exceptions. Keep the cabinet decision separate from the logistics provider’s service scope so a complete equipment quote does not conceal an unpriced warehouse dependency.
DEPOT RECORD 11
Applications
For a hypothetical mixed pallet, the supplier sends a contents message with the agreed case identifiers and counts before delivery. At arrival, the receiver scans the logistics reference and follows the agreed inspection procedure. If one case is missing, the approved receipt records the discrepancy rather than adding the entire dispatched quantity automatically.
For a hypothetical route split, accepted cases are assigned to two route loads. Preserve the relationship to the original receipt in the operating record. If a new physical logistics unit is built and labeled, obtain the provider’s corresponding record. This guide does not instruct the buyer to invent live SSCC numbers or change existing labels.
For a hypothetical unchanged pallet passed to a different carrier, the carrier-related segment can change without treating the unit as newly created. The reviewed guidance preserves the existing SSCC in that segment operation. Ask the labeling owner to show the actual procedure and ensure the unit reference remains understandable to the receiver.
For a hypothetical delayed message, identify the arriving unit and use the agreed exception route. The source recommends including the treatment of a delivery without ASN in the contract. The operator’s receiving policy should identify whether stock is held, manually checked or otherwise processed, with the responsible approval recorded.
At route return, reconcile the cabinet-loading and unused-stock records according to the chosen process. An SSCC relationship can support the earlier logistics link, but it does not by itself demonstrate the contents of a machine after customer purchases. Keep the evidence at the level the process actually observes.
DEPOT RECORD 12
FAQ
Does an SSCC identify every retail pack on the pallet?
It identifies the specific logistic unit. The related contents message or other agreed record supplies the item details. It is not presented as an individual-pack identity.
Can one content GTIN describe a mixed pallet?
The reviewed guide distinguishes a heterogeneous unit that is not itself a trade item and advises against GTIN-related contents information on its logistics label. It encourages electronic contents information linked with SSCC. Review traded-unit exceptions with a GS1 specialist.
Does scanning the label prove the delivery is complete?
The inspection and acceptance procedure depends on the supplier-receiver agreement. The receiver may need to check contents and damage, particularly for multiple products. A scan alone is not physical proof.
Do these WEIMI products include an SSCC receiving interface?
That capability is not established by the reviewed public listings. Request a configuration-specific interface demonstration and written scope if it is required.
Should a new carrier label always create a new SSCC?
The guideline preserves an existing SSCC when label segments are added or replaced. Creating a rebuilt logistic unit is a separate operation. Have the responsible labeling specialist define the correct procedure.
Are the six-month and twenty-four-month figures proven returns?
No. They follow explicit assumed labour times, activity counts and a planning allowance. Actual fees and measured receiving performance are needed for a business case.
DEPOT RECORD 13
Final Recommendation
Specify four connected records: the logistics-unit identity, its contents message, the approved receipt outcome and the later stock allocation. Confirm the packaging level and preserve useful relationships when stock is stored, split or rebuilt. Give missing-message, damage and repeated-scan cases a defined owner.
Use the AI fridge, WM22 and PPE system as public-list candidates for the intended retail or issue format. Request separate cabinet trials and any warehouse or route interface demonstration. No model is represented as independently tested, GS1 certified or proven to provide full pallet-to-cabinet traceability.
Source boundary: this review uses the GS1 page displaying release 1.3, July 2019, and current WEIMI listings. Confirm applicable current specifications and trading-partner requirements before designing production labels or messages. No live shipment, reader, warehouse interface or logistics label was audited.
DEPOT RECORD 14
CTA
For a vending project with depot-based replenishment, provide the intended assortment, supplier packaging levels, receiving system and route-loading process. Explain whether deliveries are mixed, whether an ASN is available and where stock is split.
Discuss equipment and replenishment handoverRequest written equipment and integration scopes with responsibilities, sample data, exception handling and acceptance evidence. Approve the flow on the actual systems rather than treating a readable pallet label as proof of an automated fleet.
