Business website & operations platform
8 minute readMaster Vending
A service website and a working vending operations platform, connecting route planning, warehouse stock, mobile machine servicing, coin control and financial reconciliation.
Overview
The project at a glance
The problem A vending service depends on more than the machines. Customers need a clear way to request an installation; the team needs to coordinate products, warehouses, vehicles, routes, servicing and money across several people and locations.
What I built I designed and developed the Master Vending service website and VMMS, a Next.js and Supabase application with separate workspaces for administrators, warehouse staff and field operators. The app connects route assignments, replenishment requests, stock movements, machine visits, coin wallets and reporting.
What needed care Physical handoffs need reliable records. A delivered request is distinct from a confirmed receipt; servicing is distinct from administrative collection and reconciliation. Role checks, database policies and transactional functions protect the stock and money involved in each step.
What it makes possible The team can follow work from preparation to field execution and review the stock and financial records it produces. The screenshots use the actual application components with synthetic demonstration data; figures illustrate the features and are not business performance claims.
Brief
Connect the business people see with the operation behind it
Master Vending supplies coffee, snacks and drinks to workplaces in Antofagasta, Chile. The project covers both the customer-facing service and the daily work needed to keep that service running.
I built a public website that explains the offer and collects useful proposal enquiries, alongside VMMS, the operational web application. Inside VMMS, administrators coordinate the fleet, warehouse staff manage inventory and requests, and operators follow their assigned work on mobile.
The central design problem was connecting those responsibilities. A product leaves a warehouse, reaches a vehicle, enters a machine and eventually becomes part of a sales or collection record. Each handoff needs context: what moved, where it went, who handled it and which stage is complete.
- Two audiences: prospective customers and the team delivering the service
- Three workspaces shaped around actual responsibilities
- One connected sequence of operational records
- Trace each handoff from warehouse stock to machine sales
Website
Turn interest in a machine into an informed enquiry
The public website explains installation, replenishment and maintenance in practical terms. Visitors can compare coffee, snacks and combined machine options, understand the space assessment and find answers about costs, coverage and ongoing service.
The proposal form asks for company and contact details, region, machine interest, location and the number of people using the premises. Those details give Master Vending a starting brief for assessing the site and recommending a solution. WhatsApp offers a direct alternative for a conversation.
The website also introduces VMMS to other vending businesses. It separates the local vending service from the enterprise software offering, which is presented publicly as in development with an early-access enquiry. Installation remains subject to assessment.
- Machine options connected to the customer’s setting
- A structured enquiry with location and workplace context
- Clear service expectations before an installation is agreed
- Separate local vending services from software early access
Routes
Plan the fleet, then give each route an owner
The administrator dashboard combines recorded sales and units with machine and operator counts. Pending requests, deliveries to prepare and maintenance work provide direct routes into the tasks needing attention.
Route planning turns a list of machines into an ordered set of visits. An administrator creates a draft, selects and orders the stops, publishes the route, and assigns it to an operator with an assignment period. The route list shows publication state, responsibility and progress, so the office can distinguish work being prepared from work already underway.
Operators receive the work assigned to them rather than the whole administrative interface. If a route needs to be reset or reassigned, that remains an administrator responsibility. Completing a machine visit and completing the associated route stop are separate steps, making the route’s progress explicit.
- Draft, publish and assign routes with a responsible operator
- See completed and outstanding stops
- Keep planning and exception handling with administration
- Distinguish machine servicing from route-stop completion
Inventory
Know where stock is before sending it into the field
VMMS treats stock as something held in a location: a main warehouse, a mobile store such as a vehicle, or another operational location. Separate destinations for suppliers, waste and consumption preserve the reason products enter or leave the operation.
Warehouse staff can inspect locations, product quantities and movement history. Replenishment requests connect warehouse preparation to the operator’s mobile stock, while procurement requests cover supply coming into the warehouse.
Inventory changes retain an accompanying movement record. The underlying transaction updates the physical quantity and its explanation together; a multi-item operation with insufficient stock is rejected as a whole. Corrections record the change in balance and a note, so the history remains useful when someone needs to explain a discrepancy.
- Stock separated by warehouse and mobile location
- Movement history explains transfers, consumption and corrections
- Inventory quantities and ledger records change together
- Reject multi-item transfers when available stock is insufficient
Handoffs
Separate what was requested, approved, delivered and received
An operator requests replenishment for their mobile store. The request keeps the source, destination, products and quantities together. The reviewing team can check availability, approve quantities and prepare the delivery; an approval can be partial rather than an all-or-nothing promise.
The lifecycle makes each handoff visible: pending, approved, delivered and confirmed. A delivered request is still waiting for the recipient to check what arrived. For an operator request, the requesting operator confirms receipt; for warehouse procurement, the requesting warehouse administrator does so.
Confirmation updates stock and its movement records together. Repeating the same confirmation does not receive the goods twice. Detail views preserve requested, approved and delivered quantities, item notes and the request history, giving both sides a shared reference when the physical delivery differs from the original request.
- A request has an explicit origin, destination and recipient
- Partial approvals and delivered quantities stay visible
- Recipient confirmation completes the stock handoff
- Repeated receipt confirmation cannot add the same stock twice
Mobile
Put the next stop and its machine within reach
The operator workspace is designed around a phone. “Mis rutas” shows assigned work, assignment context, route progress and the next stop. The operator can open the machine from that stop instead of searching through the fleet.
At the machine, the interface connects the assigned mobile store, current readings and product layout. Each slot shows its product, current quantity, capacity and position. During an active visit, revised slots make progress visible while stock changes are recorded against the visit.
The machine also has technical checks for payment devices, maintenance and signal. After recording the work, the operator returns to the route and completes the stop. A skipped stop requires an explanatory note, preserving the difference between work completed and a visit that could not proceed.
- Phone layouts for assigned routes and machine servicing
- Slot-level quantities and revised status during a visit
- Stop completion and skip notes keep route progress accountable
- Technical checks cover payment devices, maintenance and signal
Supplies
Carry the right products and keep change accountable
The mobile Stock view shows the operator’s own vehicle inventory, with product search, quantities and a direct replenishment request. An outstanding delivery is called out separately: goods are added to the operator’s stock when receipt is confirmed, rather than simply because someone marked them as sent.
“Mis monedas” applies the same clarity to change. The operator sees counts of $50, $100 and $500 coins and their combined value in Chilean pesos. Incoming transfers awaiting confirmation are separate from the available wallet balance.
Operators can inspect movements and request a correction when a physical count differs. Administrators review those adjustments and manage coin delivery and target balances. A coin deposit during machine service connects the operator’s wallet to the machine’s denomination balance through an auditable movement.
- Own mobile inventory and outstanding deliveries in one workspace
- Coin counts distinguished from their value in pesos
- Confirmation and adjustment workflows preserve responsibility
- Connect machine coin deposits to the operator’s wallet ledger
Close-out
Finish the physical work before reconciling the money
Machine servicing follows a defined lifecycle. Before normal operation, a machine needs an opening reading and initial stock. Normal servicing and stock reconfiguration cannot run as overlapping unfinished sessions on the same machine.
Closing a normal visit requires saved movement evidence, the returned coin float (including an explicit zero where appropriate) and valid cumulative closing counters. The expected collection comes from the counter change less the return-coin float. An operation with saved stock changes cannot be cancelled in a way that discards those movements.
The assigned operator records the service and close-out. The administrator then records the cash/card collection and reviews the financial result. The collection view keeps expected and recorded amounts, differences and reconciliation status together. That distinction prevents a completed service visit from being mistaken for a financially reconciled one.
- Commissioning, servicing and reconfiguration have distinct states
- Counter-based close-out retains the stock and coin context
- Administrative collection is separate from operator servicing
- Preserve saved stock movements through the visit lifecycle
Reports
Use the operational records to ask better questions
Reporting brings together sales, products, machines, customers, stock, movements, collections and adjustments. Date ranges and filters let an administrator move from a broad period to a particular machine or product.
The sales view compares units, revenue, costs and estimated gross profit by product and machine. This makes the relationship between the headline indicators and the underlying rows visible. Browser reports and PDF output support review beyond the working screen.
Cost-based figures have an important boundary: they use the current catalogue cost, rather than a historical cost captured for every sale. Estimated gross profit also excludes overheads, commissions, taxes and other operating expenses. The case-study figures are synthetic examples used to show the interface, not measured commercial results.
- Review totals alongside the product and machine rows behind them
- Date-scoped reporting, browser views and PDF output
- Estimated gross profit presented with its cost assumptions
- Filter reporting by period, machine and product
Access
Make responsibility part of the system
The different workspaces are backed by access controls. Server actions check the authenticated user and permitted role; database row-level policies and guarded functions enforce the same boundaries around records and transactions. An operator’s assignment, mobile store and wallet limit the work they can perform.
Stock and coin mutations use transactional operations so a successful change has matching ledger evidence. Important retry paths are designed to avoid duplicate receipts or close-out records. Automated tests cover core workflow rules and access boundaries, alongside role-based browser checks documented in the repository.
For this case study, I inspected the signed-in administrator, warehouse and operator experiences and checked the implementation’s workflow documentation. The app images render the actual source components in a local preview with synthetic identities, products, quantities and amounts. External data access and mutations were blocked during capture; the operational database was not seeded for these images.
- Role checks supported by database access boundaries
- Traceable stock and coin changes with guarded transitions
- Real application UI, clearly labelled synthetic screenshot data
- Retry safeguards prevent duplicate receipts and close-outs
The result
The team can follow work from preparation to field execution and review the stock and financial records it produces. The screenshots use the actual application components with synthetic demonstration data; figures illustrate the features and are not business performance claims.
Good work starts with the right conversation.
Let's talk about your projectGallery
The project in pictures
A different challenge. The same care.
View all work