One catalogue
Local brands per market and a choice card that works everywhere, from a single source.
Enterprise
Gift card infrastructure for global organisations
For organisations that buy through a procurement process, across several countries and several teams. This page states what works today, what is set up per account and what is not built yet.
What the platform does
One catalogue, one contract and one invoice route behind every campaign you run.
One commercial line
One proposal, one invoice route and one contact person across countries and teams.
One honest status
Every capability below carries a status, so a procurement review finds no surprises.
How to read the statuses
- Availableusable today as described
- On requestexists as a service, set up per account
- Bespokeonly as a bespoke project, assessed per case
- Plannednot built yet, no date promised
Each status is written out as a word, never carried by colour alone.
Procurement
Purchase orders, cost centres, invoicing and the procurement suites.
Purchase order on the invoice
AvailableYou pass a PO number with the request and it is carried through to the invoice.
Cost centre per line
AvailableA cost centre travels with the order and appears on the invoice line.
Ordering on invoice
AvailableBusiness orders run on invoice, with the payment term agreed in the proposal.
Consolidated invoicing
On requestOne invoice across campaigns or entities instead of per transaction — set up per account, not self-service.
PunchOut (cXML / OCI)
PlannedA catalogue session from inside your procurement system. Not built.
Ariba, Coupa, Oracle connectors
PlannedCertified connectors for the large procurement suites. Not built.
Identity and access
Sign-in, roles, approvals and user provisioning.
Single sign-on (SAML / OIDC)
PlannedLogging in with your own identity provider. Not built.
Roles and permissions
PlannedRequester, approver and viewer roles for your own users. Not built.
Approval flows
PlannedMulti-step approval before an order is placed. Not built.
User provisioning (SCIM)
PlannedAutomatic creation and removal of users from your directory. Not built.
API and integrations
Programmatic ordering, events and connections with your own systems.
Public ordering API
PlannedA documented API with your own credentials. The internal platform contract exists; the public API does not.
Webhooks on order events
PlannedOutbound events for created, delivered and redeemed. Not built.
HRIS and CRM connectors
PlannedTriggering a gift from a milestone in your HR or CRM system. Not built.
Bespoke integration
BespokeA file or system exchange designed for your situation; scope and feasibility are assessed per case.
Reporting
What you can see back per campaign, country, entity and budget.
Reporting per campaign
On requestAn overview of a campaign is produced by your account manager; a dashboard inside the product is planned.
Breakdown per country
On requestA split by destination country is delivered with the reporting on request.
Entity structure
PlannedLegal entities with their own budgets and their own reporting line. Not built.
Budget tracking
PlannedA live view of a committed budget for your own users. Not built.
Audit trail you can consult
PlannedOrder events are recorded internally; a trail you can consult yourself is not built.
Global delivery
Recipients choose their own country and currency; an IP guess is only a suggestion and is always overridable.
Unspent budget returns to you in full, and the recipient carries no currency cost.
Self-service
Requesting a quote, an account manager and ordering on invoice work today. Creating an account yourself and paying online do not; they are listed as planned rather than promised.
Requesting a quote
AvailableThe quote intake is the working route into a business order today.
A named account manager
AvailableOne contact person who handles your requests, proposals and orders.
Creating an account yourself
PlannedSigning up and managing your organisation without us. Not built.
Checking out yourself
PlannedPaying a business order online without a proposal. Not built.
Security and compliance
Codes are never stored by a storefront: an order holds a token, and the code itself is revealed only on an explicit, rate-limited request.
Every write carries an idempotency key, so a retried order cannot become a second order.
Redemption pages are excluded from indexing and from caching, because the link itself is the credential.
Implementation and support
A first conversation maps volume, countries, procurement route and the systems involved.
Your account manager stays the single point of contact after go-live, for ordering as well as for questions from recipients.
Questions from procurement
- Can we order through Ariba, Coupa or Oracle?
- Not yet. PunchOut and connectors for the large procurement suites are planned and not built. Ordering runs through a proposal, with your purchase order number and cost centre on the invoice.
- Is there single sign-on?
- No. Single sign-on, roles, approval flows and SCIM provisioning are planned. Access today runs through your account manager.
- Is there an API?
- Not a public one. The internal platform contract exists, but there is no documented API with your own credentials, and no webhooks.
- How do we pay?
- On invoice, with the payment term agreed in the proposal. Discount is determined per request and stated per line in the proposal.
Schedule a conversation
Tell us briefly where you stand. You get an enterprise account manager who works with your procurement and IT.
Ordering for 500 recipients or fewer, and not through a procurement system such as Ariba, Coupa or Oracle? Then the regular quote intake is faster. Request a quote