Buying credentials for several properties in several markets introduces a set of problems that have nothing to do with the credential. Separating those from the specification is most of the work, and doing it in the wrong order is what fragments a group order.
Separate the product decision from the logistics decision
The specification question is what the credential must be: construction, technology, artwork, quantities. The logistics question is who imports it, into which market, under whose documentation, and on what schedule. They are frequently discussed as one conversation and they have different owners and different timelines.
Groups that keep them separate order once and distribute. Groups that merge them tend to end up with each property ordering its own version, which multiplies artworks, multiplies minimums and produces a fleet of credentials that no longer look related.
One artwork across properties, or one per property
This is the decision that determines the cost of a group programme. Minimum order is 500 pieces per artwork, so a group of six properties each with its own design is six counts; the same group sharing one artwork with a colour per property may be far fewer.
The right answer depends on whether the properties are marketed as one brand. Where they are, a shared artwork is both cheaper and more coherent. Where they are genuinely distinct brands, accept the multiplication rather than forcing a compromise that satisfies nobody.
Questions that settle the group structure:
- Are these properties presented to guests as one brand or as separate ones?
- Does any property need a credential the others do not — a different construction, not just a colour?
- Who holds stock: each property, or one location that distributes?
- Who approves artwork changes on behalf of the group?
Importer of record, per destination
Each destination has a party responsible for the import. In a group that party is not always the same, and it is not always the property — sometimes it is a management company, sometimes a local agent.
Establishing who it is per destination before the order is placed removes the most common cause of goods sitting somewhere while somebody works out who is responsible. We supply the documentation that accompanies goods; we do not act as importer, and we cannot resolve that question on a property’s behalf.
Documentation language and format
Material declarations and supporting records may need to be presented in a local language, or in a particular format, to satisfy a procurement or customs process. That is a straightforward request when it is made before production and an awkward one afterwards.
Ask each destination what it needs, once, at the specification stage, and carry the answers into the order rather than discovering them at delivery.
Replenishment without fragmenting the run
The failure mode in multi-market programmes is that one property runs low, orders alone, and the group ends up with two subtly different runs of the same credential. Colour drifts, a component changes, and two properties that should look identical no longer do.
The fix is a shared reorder record — approved sample, artwork revision, colour reference, credential input — held by whoever approves for the group, and a replenishment plan that consolidates rather than reacts.
No duty rates, no per-market transit times and no customs fees appear on this site. Those change by destination, by shipment and by date, and a number published here would be wrong for somebody. We describe the process and the documentation instead.
Regional considerations for multi-market buying
Buying for properties in more than one market introduces variables that have nothing to do with the product. Separate them from the specification and answer them explicitly.
- Do the material claims need supporting documentation in the local language, and in what form?
- Which party is the importer of record for each destination, and does that differ between properties in one group?
- Is the same artwork and construction used across markets, or does each property need its own approved reference?
- How is replenishment planned so that one slow destination does not fragment the production run?
Compatibility is confirmed against the property’s lock system, credential technology and encoding requirements before production. We do not claim universal compatibility.
What to send with an enquiry
Include the installed system model, an existing credential sample where possible, quantity, expected wear period, guest types, controlled zones and artwork direction. For material-led options, state the evidence or production documentation your procurement team expects.
FSC-certified material options available with supporting production documentation.
No named hotel or customer project is used as proof. The reasoning behind that stance is set out on the about page.