A company customer asks whether employees can use a workplace allowance at the cabinets an operator already runs. Before proposing a rollout, choose one installation where the employer policy, device connection and period records can be tested together.
The purpose of this first stage is to establish how the service behaves and who handles exceptions. It should produce an expansion decision with evidence. The employer and operator can use the initial installation to review responsibilities and records.
In this guide
Choose a site that answers a real operating question
Select an employer sponsor, a finance contact, an operator lead and the exact cabinet model. Define the employee group and the intended use: lunch during a shift, a general shopping contribution or another specified programme. Confirm access hours, product availability and the support route for that site.
Avoid selecting a test purely because it is easy to demonstrate. If the proposed service includes evening shifts, those users and support hours belong in the plan. If it includes several product categories, the test catalogue should reflect the categories that will actually be allowed.
Record what stays outside the first stage. A successful test at one model and location is not evidence that another manufacturer or payment arrangement works. It can still be a useful basis for deciding what to test next.
Write the commercial responsibilities before the first purchase
The employer should approve eligibility, contribution and the treatment of unused entitlement. The operator should explain the product service, customer support and settlement arrangement. The software and device parties should confirm the integration boundaries.
State who pays whom and what record supports the amount. An allowance visible to an employee is not necessarily money already transferred to the operator. Decide how fees, refunds and unresolved purchases will be reviewed without presenting a draft process as a final accounting or tax conclusion.
Use the funding and allowance guide to separate company entitlement from employee payment. Where the proposal uses a regulated local meal-benefit arrangement, obtain the relevant local review before describing it that way to employees.
Verify the whole purchase path
Manufacturer materials can help identify the available platform functions. For example, Selfly Cloud describes product-catalogue and operating data. They do not replace confirmation of the precise API access and transaction route used by a third-party application.
For the selected installation, follow a user from company enrolment to a cabinet session, a final basket and the resulting records. Distinguish opening a door from completing a purchase, and completing a purchase from paying the operator. Keep a shared reference wherever records pass between systems.
MoiPass has an existing Selfly connection. Other models require their own assessment; Husky is reviewed by model. Check the current connection scope when preparing the corporate proposal.
Review the purchase flow
Ask the employer and operator which purchase and reporting steps matter for the proposed installation. Review the final purchase record and how a customer can report a problem. Any acceptance criteria should be agreed by the parties for that installation.
Measure completion and exceptions with defined denominators
Agree measures before the test starts. Useful candidates include eligible employees enrolled, attempted sessions, completed purchases, unresolved records and support requests by cause. Define what counts as an attempt and whether retries belong to the same purchase.
Separate adoption from financial correctness. An employee choosing not to buy is different from a failed session. A high purchase count cannot establish that every allowance deduction is correct. Track whether completed records reconcile and how long unresolved cases remain open.
Set any pass threshold with the employer and operator. This guide provides no benchmark, forecast or claimed customer result. A small test may reveal a serious data issue even when most purchases appear successful; the expansion decision should consider the type of failure, not only an aggregate percentage.
Give employees one practical support instruction
Explain where the allowance can be used, which products it covers, where the purchase record appears and how to report a problem. Name the route that receives the request even if another supplier ultimately investigates it.
Keep personal-data explanations tied to the actual setup. The European Commission’s employee-facing information principles describe the kinds of processing information individuals should receive. Optional tracking should have its own explanation; employees should not need to enable it merely to use the agreed shopping allowance.
Close with an expansion decision and an owner for open work
At the review, compare the accepted cases, period records and unresolved items. Decide whether to continue at the same site, change the arrangement, test another model or expand. Record conditions on the decision so a later team knows what was actually established.
The operator solution sets out how MoiPass can be discussed as part of a company offer. For a product demonstration, send the cabinet model, employer use case and proposed funding arrangement. That is enough to begin a scope review without presenting an untested rollout as ready.