Summary: Vendor tags help categorise and filter vendors in AXP (such as restaurants, touring agencies, and transportation providers) — for example by type, atmosphere, cuisine, or amenities. Tags are managed at the brand level by the Alliants team. If you need a tag that doesn't currently exist, please ask your brand admin to submit a Change Request to Alliants with the details below.
Permissions Required: Brand Admin (to submit a request to Alliants)
How vendor tags work
Tags in AXP are set at the brand level, which means:
Any tag created for your brand is available across all of your locations.
New tags can be applied to any existing vendor — not just new ones.
Changes appear in AXP almost immediately after the tag is created.
Tags are grouped into categories (e.g. VENDOR TYPE, HIGHLIGHTS, ATMOSPHERE, CUISINE). When requesting a new tag, you'll need to specify which category it belongs to — or request a new category if none of the existing ones fit.
How to request a new tag
Vendor tags cannot be added directly in AXP. To request a new tag, please ask your brand admin to contact the Alliants support team via Help & Support tab and include the following information:
Field | What to provide |
Display Name | The name of the tag as it should appear in AXP (e.g. "Halal certified") |
Category | The category the tag should sit under (e.g. VENDOR TYPE, ATMOSPHERE). If you need a new category, include the category name and colour preference. |
Source Keys | Only needed if your property uses a connected PMS or CRM for the vendors. See the section below. |
What are Source Keys?
Source Keys is an optional field that tells AXP how to match this tag to equivalent codes in your connected system (such as a Property Management System or CRM).
If your property integrates with one of the following systems, providing a Source Key allows AXP to automatically apply the correct vendor tag when syncing data from that system:
Key name | System |
| AXP (always required — this is the tag's internal identifier) |
| iReckonu |
| SevenRooms |
| HAPI |
| OHIP |
| StayNTouch |
Example: If your property uses iReckonu and their system calls a vendor type "Fine Dining", you would provide:
axp_code: "Fine Dining"
ireckonu_code: "Fine Dining"
If you are not sure what code your connected system uses, you can have it blank as it is not sourced.
🗒️ Note: If your property does not use any of the integrations listed above, you only need to provide the axp_code. This is the tag's display value as it will be stored internally in AXP.
Common Questions
Q: Can I add vendor tags myself in AXP?
A: No. Vendor tags are managed by the Alliants team and cannot be created directly in AXP by brand admins or conversers. To add a new tag, your brand admin needs to submit a change request to Alliants support with the tag name, category, and Source Keys (if applicable).
Q: Will a new tag apply to my existing vendors?
A: Yes. Once a tag is created, it becomes available across your brand and can be applied to any existing vendor — there is no restriction to new vendors only.
Q: Are tags shared across all my locations?
A: Yes. Tags are set at the brand level, so all locations within your brand can see and use them.
Q: How quickly will the new tag appear after the request is processed?
A: Changes take effect almost immediately after the Alliants team creates the tag — no refresh or re-login is needed.
Q: Do I need to provide Source Keys?
A: Only if your property uses an integration with iReckonu, SevenRooms, HAPI, OHIP, or StayNTouch. Source Keys allow AXP to automatically match incoming data from those systems to the correct tag. If you don't use any of these integrations, you don't need to worry about this field.
Q: What is a tag category, and do I need to create one?
A: Categories group related tags together — for example, VENDOR TYPE, HIGHLIGHTS, or ATMOSPHERE. If your new tag fits into an existing category, just name it in your request. If none of the existing categories fit, you can request a new one at the same time and specify a name.