Treat the facility as part of the record
Before reviewing inventory, select the facility where the work belongs. Confirm the product identifier within that context. A product name shared across locations is not enough to justify using the same quantity, parent or label profile. Make the selected facility part of the conversation whenever work moves between operators.
This is also a useful check when records appear to disagree. One person may be looking at another facility, or at information read at a different time. Start with those possibilities before deciding that the underlying stock changed. Waputu applies facility authorization to protected work and keeps the source identifier associated with the job. That gives a team a specific context to verify rather than relying on whichever view was last open.
Separate organization isolation from facility permissions
A Waputu organization receives its own application and database through the verified signup process. Within that customer workspace, team roles and facility access determine the work a person can perform. Those are different boundaries: isolation separates customers, while facility permissions organize access inside the customer’s operation.
Do not use a shared owner account as the normal way to work across locations. Invite staff and assign the access appropriate to their responsibilities. Review permissions when a person changes locations or duties. An account that can sign in should not automatically be assumed to have access to every facility or every protected action. Owners and administrators complete the required MFA flow for protected access, adding another deliberate step around account administration.

Build a repeatable opening routine
At the start of work, choose the facility, check source freshness and inspect unfinished jobs. Identify the lots needed for the day and note any unresolved differences before starting another operation. This routine is short, but it can prevent a second operator from unknowingly beginning work that someone else already attempted.
A shared operating checklist is more useful when it asks for observations rather than a vague confirmation that everything looks good. Check the source identifier, relevant quantity, time of the read and current job status. If there is a mismatch, preserve those details and decide who will investigate it. Avoid reconnecting an account or starting a new split as a first response to a record that simply needs a more careful review.
Standardize the process, review the product
Teams can use the same label-preparation process across locations while still reviewing the facts of each product. Standardize how an operator checks the manufacturer, source lot, lab reference, quantity and QR destination. Keep the actual values specific to the product and job instead of making a universal template that silently carries another location’s assumptions.
Printer setups deserve the same attention. A PDF prepared with the correct physical dimensions can still be scaled by a driver or clipped by a printer’s margins. Test each intended printer and stock combination, then preserve the setup instructions. Waputu supports custom roll and sheet output; the device must still support the media, printable area and required color. A successful proof at one location does not establish acceptance for a different printer at another.

Make the handoff explicit
When one person reviews inventory and another prints, the handoff needs more than a filename. Identify the facility, the selected lots, the number of product labels and the sequence of separators. For ten lots of fifty items, the print job contains five hundred product labels and ten internal separators. Keep that order intact while moving the stack to packaging.
If a job needs a reprint, use the recorded PDF rather than creating another sublot. If the underlying facts need correction, prepare a new label job and tell the next operator which output replaces the earlier one. These are different actions with different meanings. An explicit handoff prevents a reasonable request such as “print that again” from turning into unnecessary inventory work or an undocumented change to product information.
Plan expansion from demonstrated needs
Before adding another facility to a routine, identify who will administer it, which staff need access, which inventory tasks they perform and what printers they use. Demonstrate those tasks with the proposed setup. Check a facility boundary, an interrupted job and a physical label sample, not only the appearance of the dashboard.
Use the current product and commercial terms when evaluating capacity or future plans. Do not assume a location limit, a price or an integration because it appeared in an early design. The useful question is whether the team can complete its actual workflow with appropriate access and a clear result. Waputu’s resource guides and support instructions explain the implemented process; broader operational questions should also be checked against the state’s current published requirements.
Source: CCD laws, rules and regulations.
