Cloud System and Commercial Configuration
Addendum for TCN-CSC-8C(V49)
Executive Summary
Two new primary artifacts materially reduce uncertainty in the earlier ecosystem analysis: (a) a bilingual
user manual for the Yunshu Vending Machine Management System V2.0 (cloud back office), and (b) a
signed sales contract/quotation for TCN-CSC-8C(V49) that clarifies configuration-specific inclusions/
exclusions (notably 4G connectivity and payment hardware not included) plus warranty and legal
constraints. fileciteturn0file0 fileciteturn0file1
From the cloud manual, the vendor cloud system is explicitly named Yunshu Vending Machine
Management System V2.0, with a public login URL www.ourvend.com, multi-language UI (Chinese/
English/Vietnamese), QR-code login support, role-based subaccounts, and operational dashboards covering
sales analytics, inventory/replenishment suggestions, delivery records for reconciliation, alarms, and noncash transaction records. Several high-impact capabilities are marked as VIP (paid) add-ons, including
remote item/slot edits (names/images/prices/capacity), remote device configuration (e.g., drop detection,
change-making policies, temperature parameters), branded UI customization, and an advertising workflow
that changes the payment waiting page advertisement after platform review/approval.
fileciteturn0file0
From the sales contract, the seller is entity["company","Changsha Zhonggu Intelligent Equipment
Manufacturing Co., Ltd.","ningxiang, hunan, cn"], located in entity["city","Changsha","hunan,
cn"], entity["state","Hunan","province, cn"], entity["country","China","country"], with pricing
expressed as FOB and a stated one-year warranty under proper operation. The contract’s BOM-style
description confirms MDB/DEX support, a 4G module, and an “online inventory and sales system,” but
explicitly states the delivered machines can be supplied without a payment system**, leaving the buyer
to install local payment hardware. fileciteturn0file1

Yunshu Cloud System Identification and Access
The cloud platform in your bilingual PDF is explicitly titled “Yunshu Vending Machine Management
System V2.0” and labeled as a User Manual. It includes versioning metadata: V2.0 with an update date of
June 15, 2018, and it distinguishes Standard functions + VIP functions. This date strongly suggests the UI/
feature descriptions may be “platform baseline” documentation and may not reflect any post-2018 UI
modernization—an important risk to validate during vendor demo/testing. fileciteturn0file0
The manual provides a concrete access path:
• Web login portal: www.ourvend.com (browser login via username/password; QR-code login also
supported). fileciteturn0file0

1

• Language support: UI language switch at top of page, explicitly listing Chinese, English,
Vietnamese. fileciteturn0file0
• Mobile workflow via WeChat official account: the manual instructs scanning a QR code to follow a
WeChat official account (“Join Yunshu”) and binding cloud credentials to view data in a mobile back
office. fileciteturn0file0

Access and authentication implications
The manual demonstrates account/password login and QR-based login, plus a WeChat account–binding
flow. It does not document MFA, SSO, password policy, session lifetimes, IP allowlisting, or audit
requirements (all security-relevant omissions for enterprise deployment). Those controls should be treated
as unspecified until verified via a live tenant configuration review. fileciteturn0file0
image_group{"layout":"carousel","aspect_ratio":"16:9","query":["Yunshu vending machine management
system V2.0 ourvend.com dashboard","ourvend.com Yunshu VMMS login page","Yunshu vending machine
cloud platform advertisement module screen"],"num_per_query":1}

Operational Capabilities and Telemetry Model
The manual describes a “Daily Operation Monitoring (Home Page)” dashboard summarizing fleet KPIs such
as today/yesterday/weekly/monthly sales, online/offline counts, abnormal machine count, out-ofstock machine count, and charts for payment-type mix and an eight-day sales trend curve.
fileciteturn0file0
A separate “Status Monitoring” module describes a telemetry model that includes:
• Network status
• Temperature
• Door open/close status
• Drop detection status
• Banknote/coin device status
• Slot/track status
• Traffic usage (“flow”)
• Timestamp of last data upload
• Deployment address
• Assigned administrator(s) fileciteturn0file0
This is useful for scoping what the machine is expected to report upstream, but the transport protocol,
encryption, and device identity mechanism are not documented in the manual (unspecified).
fileciteturn0file0

2

Records, reconciliation, and exports
Several record types are defined with explicit reconciliation intent:
• Sales details: query by machine/group and date range; exports to Excel; includes links to transaction
turnover, sales summary, card swipes, delivery records, door open/close flow, replenishment records,
and receivables. fileciteturn0file0
• Delivery records (explicitly labeled “Important, used for accounting checking”): query within seven
days, filter by payment method and state, and export to Excel. It also stresses that statistics are
based on server time (machine time vs server upload time can differ significantly after outages).
fileciteturn0file0
• Replenishment suggestion: out-of-stock checks and an exportable replenishment report.
fileciteturn0file0
Constraint worth noting: multiple query screens specify date ranges within 7 days, implying either (a)
performance constraints, (b) UI defaults with expandable options not documented, or (c) a product
decision. Treat longer retention/query capability as unspecified until verified in your tenant.
fileciteturn0file0

Payments, Settlement, and Refund Workflows
Payment method binding and settlement sensitivity
The back office includes “Setting of Payment Parameters,” described as binding payment methods fleetwide for a user’s machines, including WeChat, Alipay, Jingdong, Bestpay, 融E联 (E-banking / Rong E Lian),
and UnionPay. The manual adds an explicit warning that this “involves fund settlement” and instructs
operators to consult platform customer service before filling in parameters. fileciteturn0file0
This supports two important inferences (explicitly marked as inferences): - Inference: The cloud platform
likely supports multiple acquirers/aggregators or settlement modes, and misconfiguration could misroute
settlements.
- Inference: Payment integration is not purely “plug-and-play” at the machine level; it is an operator
onboarding/configuration process with platform support requirements.
Both inferences derive from the “settlement warning” language, but specific integration contracts and API
specs remain unspecified. fileciteturn0file0

Non-cash turnover records and manual refunds
The “Non-cash Turnover Records” module enumerates supported non-cash streams and allows refund
handling when vend fails after successful payment and auto-refund fails. The listed payment streams
include WeChat, Alipay, 云投币/Coinect, ICBC E‑banking, Bestpay, ChinaUMS, and Ping An E‑payment.
fileciteturn0file0
Operationally, this is significant because it implies: - The back office tracks order numbers per non-cash
payment. fileciteturn0file0

3

- There is an operator-facing pathway to issue refunds based on payment order number under certain
failure conditions. fileciteturn0file0
Unspecified: Whether refunds are “native” API refunds through each payment provider, mediated through
Yunshu as aggregator, or executed via a separate ops process; the manual does not provide technical
settlement/refund architecture. fileciteturn0file0

Published settlement reports
The report module includes a WeChat Settlement Report and an Alipay Settlement Report, each with
eligibility constraints (e.g., WeChat personal-collection users; Alipay manual settlement vs instant arrival
accounts). fileciteturn0file0

VIP Monetization Model and Advertising Workflow
The manual repeatedly labels certain modules as “VIP Function” and states that VIP functions are paid
features that can be enabled per module. fileciteturn0file0

What appears to be standard vs VIP (paid) in Yunshu V2.0
Capability area

Described behavior

Labeled paid/VIP?

Notes

Fleet
dashboards

Sales KPIs; online/offline
counts; charts

Not labeled VIP in
the described
sections

Treat as baseline unless vendor
contract says otherwise.
fileciteturn0file0

Status
monitoring

Network/temperature/
door/drop sensor/cash
module state, traffic
usage, last upload

Not labeled VIP in
the described
section

Strongly implies telemetry
exists even without VIP.
fileciteturn0file0

Track (slot)
management

Remote edit of item
name/image/price/
capacity; clone across
machines

Explicitly says
remote
modifications are
a paid feature

The manual says changes sync
to machines only when remote
function is enabled.
fileciteturn0file0
Ads are tied to “waiting page
for payment with mobile code

Upload ad image to
Machine
advertisement

Remote
configuration
parameters

payment waiting page
after paid enablement
and approval
Remote drop detection,
change-making rules,
main/aux cabinet
temperature, lock-onabnormality, accepted
cash types, etc.

VIP

VIP

4

scanning,” not necessarily fullscreen takeover.
fileciteturn0file0

High operational value; should
be costed and tested.
fileciteturn0file0

Capability area

Described behavior

Labeled paid/VIP?

Notes

White-label UI
branding

Custom logo, agent
trademark

VIP

Relevant if you intend to resell/
white-label. fileciteturn0file0

Advertising workflow specificity
The “Machine Advertisement (VIP Function)” module is unusually concrete: enable ads for a specific
machine ID, choose duration, pay, upload an image, then wait for platform review/approval; once
approved, the payment waiting page image changes. fileciteturn0file0
Unspecified: supported image formats, file size limits, creative approval SLA, moderation policy, proof-ofplay metrics, and whether ads can run outside the payment waiting screen (e.g., idle loop on the 49"
display). fileciteturn0file0

Seller Configuration, Pricing, Warranty, and Legal Constraints from
the Contract and Quote Image
Seller identity and how it maps to the ecosystem
Your sales contract identifies the seller as entity["company","Changsha Zhonggu Intelligent
Equipment Manufacturing Co., Ltd.","ningxiang, hunan, cn"] and includes a corporate address in
**entity["city","Changsha","hunan,
cn"],
entity["state","Hunan","province,
cn"],
entity["country","China","country"]. fileciteturn0file1
Why this matters: It provides a legally binding counterparty name for procurement and after-sales
support, which may differ from the marketing/manufacturer brand names used on websites and distributor
listings. fileciteturn0file1

Configuration-specific technical clarifications in the contract
The contract line item for TCN-CSC-8C(V49) explicitly includes:
• Cooling: “with cooling gas,” “lowest 4°C (adjustable)” (exact refrigerant/standards unspecified).
fileciteturn0file1
• Dispensing types: Spiral / conveyor / pusher. fileciteturn0file1
• Display: 49-inch touch screen. fileciteturn0file1
• Sensors/standards: advanced drop sensor; “International MDB\DEX standard.” fileciteturn0file1
• Glass: “double tempered glass with heating function, no fog.” fileciteturn0file1
• Trays/slots: “Standard: 6 trays, 8 slots/tray MAX 240.” fileciteturn0file1
• Connectivity: “With 4G module.” fileciteturn0file1
• Electrical: 230V/50Hz; plug type specified per order (SAA in the contract). fileciteturn0file1
• Included software: “Online inventory and sales system.” fileciteturn0file1
• Payment hardware: “Without payment system, customer will install in local.” fileciteturn0file1
This directly resolves earlier “unspecified” items for connectivity (4G) and procurement practice for
payments (machine can ship without validators/readers installed). fileciteturn0file1

5

Pricing and commercial terms
The contract provides a concrete unit price and FOB costing structure for a specific order, including partial
logistics charges and payment terms (e.g., deposit and balance timing). fileciteturn0file1
Because commercial documents include sensitive details (personal contact info, bank account numbers),
only high-level terms are summarized here. The contract also explicitly states deposit non-refundability
and outlines delivery timelines and storage penalties under delayed pickup/payment conditions.
fileciteturn0file1

Warranty, service window, and restrictions
The contract contains a “Quality Guarantee” section committing to a one-year warranty when operated
according to the instruction manual, with free spare parts for non-man-made failures during warranty. It
also states a phone consultation service window (12 hours/day, 5 days/week, Beijing time) and includes
notable exclusions such as damage to vulnerable parts and a clause warning against outdoor exposure that
can damage the LCD screen. fileciteturn0file1
The contract includes IP/protection terms: ownership of intellectual property remains with the seller and
the buyer is prohibited from reverse engineering (surveying/mapping with third parties).
fileciteturn0file1

What the quote screenshot adds
The attached image appears to be a quote-table row for TCN-CSC-8C(V49) and shows a configuration with
4G, MDB/DEX, double tempered glass heating (anti-fog), and a price consistent with the contract, but it
differs in multiple technical parameters (e.g., “without cooling gas”, tray/slot geometry 6 trays × 9 slots =
max 270, and an EU plug). Because this is not a signed contract page, treat it as configuration evidence
rather than definitive specification.

Discrepancies, Integration Impact, and Verification Checklist
Why the documents disagree on dimensions, capacity, and cooling
Across the signed contract and your quote screenshot, at least three attributes vary:
• Cooling: “with cooling gas” (contract) vs “without cooling gas” (screenshot).
• Slot geometry and capacity: 6×8 (max 240) (contract) vs 6×9 (max 270) (screenshot).
• Plug standard: SAA in the contract vs EU in the screenshot.
The Yunshu manual also frames the platform as supporting multiple machine types, including multi-cabinet
temperature settings and multiple payment flows, which aligns with the idea that TCN-CSC-8C(V49) can be
shipped in materially different configurations. fileciteturn0file0 fileciteturn0file1
Procurement/integration implication: you should treat “TCN-CSC-8C(V49)” as a base cabinet + selectable
options package. Your acceptance tests and compliance requirements must be tied to the final

6

configuration sheet for your purchase order (cooling type, slot count, modem type, plug, payment stack).
fileciteturn0file1

Prioritized verification checklist to close remaining gaps
1. Request a final per-order configuration datasheet (signed/stamped) that includes: cooling system
spec (compressor, refrigerant), exact tray planogram, final outer dimensions, and exact modem (4G
CAT and bands). (Unspecified in provided docs.) fileciteturn0file1
2. Obtain Yunshu tenant access (or a sandbox) and confirm: retention/query beyond 7 days, export
formats, API availability (if any), and VIP module pricing and enablement model per device or per
account. fileciteturn0file0
3. Clarify payment architecture: whether your deployment will use Yunshu-integrated payments
(WeChat/Alipay/UnionPay flows) or local acquirer hardware only (e.g., MDB cashless readers). The
contract indicates payment hardware can be excluded; the cloud manual indicates multi-PSP
configuration exists. fileciteturn0file0 fileciteturn0file1
4. Security assessment of the cloud plane: confirm RBAC settings (roles/subaccounts exist), password
policies, audit logs, and whether QR login introduces additional risk. The manual confirms role
management and subaccount permissions but does not document MFA or hardening controls.
fileciteturn0file0
5. Legal review: the contract prohibits reverse engineering and asserts seller IP ownership. If your
evaluation plan includes teardown, firmware analysis, or third-party security testing, negotiate
explicit allowances in an addendum. fileciteturn0file1

Appendix of Sources and Annotations
Primary internal documents provided by you
• Yunshu Vending Machine Management System V2.0 – bilingual user manual (uploaded PDF).
Used to identify the cloud platform name, login URL (ourvend.com), module list, VIP paid features,
telemetry fields, payment record types, and ad workflow. fileciteturn0file0
• Sales Contract No. CZG-WXS-2511-0189-JZ (2025-11-28) (uploaded PDF). Used to confirm seller legal
entity, configuration-specific features (4G, MDB/DEX, anti-fog heated glass), explicit exclusion of
payment hardware, warranty terms, service hours, and restrictions on reverse engineering.
fileciteturn0file1
• Vendor quote screenshot (uploaded image). Used as non-contractual evidence of configuration
variability (cooling/no cooling, slot geometry, plug standards) and price consistency signals; used
cautiously because it is not a signed specification.

7

