Setup Reference
The settings worth getting right before you hand ContainerQ to real users: who gets access to what, your GS1 Company Prefix, and where container-type defaults live. This is a reference, not a walkthrough — for a guided first run, see build your first pallet.
Permission sets
Assign every user a permission set that matches what they actually do, not the broadest one available:
| Who | Assign |
|---|---|
| Anyone who packs, moves, or ships containers | A full-access role — everything needed to build, pack, move, nest, and print a container’s label. |
| Anyone who only needs to look up a container’s contents | A view-only role — read access to a container’s record and contents, with no ability to change them. |
Most warehouses need both: operators on the floor get the full-access role, and anyone in customer service, planning, or management who just needs to check what’s on a pallet gets the view-only role instead. Getting this split right matters more than it looks like it would — a view-only user who’s mistakenly given the full-access role can post activity against containers they were never trained to handle, and that activity lands on the ledger just as permanently as anyone else’s.
Your GS1 Company Prefix
A GS1 Company Prefix is the block of digits GS1 licenses to your organization specifically — it’s what makes every SSCC ContainerQ issues globally unique, not just unique inside your own warehouse. If your organization doesn’t already have one, it’s obtained through GS1 or your country’s GS1 Member Organization, separately from ContainerQ itself. Enter your real, verified prefix in setup so the identifiers on your labels are genuine, trading-partner-ready numbers rather than placeholders.
Until a real, verified GS1 Company Prefix is entered, every label ContainerQ prints carries a visible watermark marking it for internal use only. That’s deliberate: labels printed during setup, testing, or training can never be mistaken for a real, trading-partner-ready identifier once your warehouse starts shipping for real. The watermark disappears automatically once a verified prefix is in place — there’s no separate switch to flip, and no old labels to reprint retroactively; only labels printed afterward carry the change. See labels and barcodes for what’s actually encoded once that prefix is live.
If your organization’s prefix ever changes — a reissue, a corporate restructuring, a new GS1 registration — update it in setup as soon as the new prefix is confirmed. Containers labeled under the old prefix keep their already-assigned SSCCs; only new assignments use the updated number. An SSCC is permanent to the container it was assigned to, so a prefix change is never retroactive.
Container-type and size defaults
If your organization defines a standard set of container types — pallet, tote, carton, and so on — with default sizes or capacities, that reference data lives wherever your Business Central administrator has set it up as part of your organization’s own configuration. It’s admin-side setup, not something an individual operator chooses per container; ask your administrator where your organization keeps it if you don’t already know. Not every organization uses defaults at all — if yours doesn’t, you can choose a container type freely each time you build one, with no default to look up.
Before your first real container
Three things worth confirming before you hand ContainerQ to operators for real work, in order: that item tracking is configured correctly on the items you plan to license-plate (package tracking where you want Package bind, standard lot/serial tracking otherwise — does Business Central have license plates? explains what that native tracking layer does and doesn’t cover), that permission sets are assigned to match what each user actually does, and that your GS1 Company Prefix is entered and verified so labels stop carrying the internal-use watermark. Getting these three right before go-live avoids the two most common setup mistakes: an item quietly ending up Positional-bound when Package bind was intended, and a warehouse shipping real product on watermarked, internal-use-only labels because the prefix step was skipped.
With permissions, a real prefix, and (if you use them) container-type defaults in place, the setup is done. The how-to guide walks through building an actual container end to end, from install through a verified ledger match — worth doing once yourself before you hand the process to your team.