Swag store integrations: SSO, HRIS, CRM, procurement and warehouse

Swag store integrations connect the storefront to the systems that already hold the answers: identity and SSO for login and rights, HRIS for credits and lifecycle events, CRM for customer and sales campaigns, rewards tools for balances, procurement and finance for purchase orders and approvals, and warehouse and courier systems for fulfilment and tracking.

The principle is simple. Every question a store has to ask is a question some other system already answered. Who is this person. Which team are they on. What are they allowed to see. What are they allowed to spend. What just happened that deserves a gift. Integration is how the store stops asking and starts knowing.

Why a swag store integrates at all

An unintegrated store works. It just makes everyone do the data entry. Someone maintains a list of who is allowed in. Someone uploads credit balances from a spreadsheet. Someone forwards orders to the warehouse. Someone chases tracking links. Every one of those tasks is a system talking to a system through a human.

Integration removes the human from the middle of the machine, not from the middle of the relationship. That distinction runs through everything below.

Three things the surrounding systems already know, and the store should not re-ask:

• Who the user is. The identity provider authenticated them this morning.
• What they are entitled to. Role, country, department, seniority and budget already live in HR and procurement systems.
• What business moment occurred. A hire, an anniversary, a closed deal, a renewal, a referral, a certification. HRIS and CRM know before anyone in marketing does.

The swag store integration map

Six categories cover almost every connection a merchandise programme needs. Most stores start with one or two and add the rest as the programme grows.

Read the table as a sequence rather than a menu. Identity decides what the store shows. Funding decides how it is paid for. Fulfilment decides what happens after checkout. The company swag store guide covers how those layers fit together.

Identity and SSO

Single sign-on is the integration that pays for itself first. It removes the account-creation step that kills adoption, and it lets the store apply rules quietly instead of asking questions at checkout.

Once identity is connected, one storefront can behave like several. Fastned uses SSO to recognise employees and allocate coins automatically on first login, so the first visit is a gift rather than a registration form. Thule uses it to give managers an ordering platform with a coin balance attached. ITI runs role-based rights, hidden products and hidden pages behind a custom SSO experience, built for an expected 35,000 to 40,000 users a year, which is a design target rather than a reported result. Zalando House of Merch is SSO-gated so only approved buyers reach the brand-approved catalogue.

Identity is the quiet layer. The people using an employee store should never think about permissions, only about what they are allowed to pick.

HRIS: credits and lifecycle events

An HRIS knows the calendar of a company better than any marketing team. Start dates, anniversaries, birthdays, departments, locations, leavers. Connecting it turns those facts into merchandise moments without anyone maintaining a list.

Bitpanda Boutique allocates employee credits through the Workday API, so a new hire arrives to a balance and an anniversary tops one up. New products are tagged automatically so returning employees can see what changed since their last visit.

Two rules keep HRIS integrations clean. First, decide which events deserve a balance before you wire anything, using the moment list in swag store funding models. Second, keep a manual route open. Automation should carry the calendar while humans carry recognition.

CRM: customer and sales campaigns

Not every store is for employees. When the audience is customers, prospects or a sales-led gifting programme, the trigger lives in the CRM. A closed deal, a renewal, a first purchase, a churn-risk flag, a referral, a completed onboarding milestone.

Connecting Salesforce to the store means a commercial event can start a merchandise workflow: send a redeem link, grant a balance, open a gated collection, or place a direct order to the customer's address. The gifting side of that pattern is covered in the corporate gifting programme guide, and the wider hub is corporate gifts.

The caution here is taste, not technology. A gift that arrives because a field changed can feel automatic. Keep the note human and the timing deliberate.

Rewards and recognition

Recognition platforms already collect the thing merchandise is good at rewarding: a peer nomination, a completed training, a wellness challenge, a sales achievement. The integration is small and the effect is large. An achievement becomes a balance, and the balance becomes a choice the person makes themselves.

Choice is the point. A recognition budget spent on merchandise the recipient selected beats the same budget spent on merchandise someone selected for them.

An HRIS-triggered onboarding allocation turns a start date into a kit like this, without anyone maintaining a joiners list.

Procurement and finance

The moment departments, managers or franchise partners order, the store stops being a shop and starts being a purchasing channel. That means purchase orders, cost centres, approval steps and invoices that finance can match.

Zalando House of Merch applies purchase-order controls and minimum-order-quantity pricing, so team orders price themselves without a quote request. ITI routes buyers to card payment or invoice depending on their role, which is only possible because identity and finance rules are connected to the same checkout.

Procurement should shape the ordering rules, contracts and controls. It usually should not own the audience experience. That split is one of the governance decisions in the pillar guide.

Warehouse and courier

This is the integration nobody sees and everybody feels. When an order is placed, the store should transfer it to the warehouse, create the shipment and labels, sync stock levels, update order status and push tracking to the recipient. No exports, no email, no spreadsheet.

Manual fulfilment is one of the eight ways a swag programme fails, because it works fine at 40 orders and collapses at 400. It also removes the data you need later: without status events flowing back, you cannot report on fulfilment performance, which is half of the framework in swag store metrics.

Stock accuracy is the other half. Replenishment decisions depend on the store and the warehouse agreeing on what exists, which is why inventory rules and integrations are designed together in swag inventory management.

One item, one order, one shipment. The warehouse and courier integrations are what keep that true at scale.

How hard is integration really

Less hard than the average procurement process implies. When a suitable API exists, integration is generally straightforward. The identity provider, the HRIS, the CRM and the courier all expect to be connected, and the patterns are well worn.

The work that actually takes time is the deciding, not the coding:

• Which attributes drive rules. Country, department, role, seniority, entity.
• Which events deserve an action. Not every field change should trigger a gift.
• Who approves what. Especially where a purchase order or an executive gift is involved.
• What happens at the edges. Leavers, transfers, contractors, agencies, multiple entities.
• Who owns the connection. IT owns security and identity, with Sunday on the store side.

Where no suitable API exists, there is usually still a route: scheduled file exchange, a webhook, or a manual step that stays manual on purpose. An integration that nobody maintains is worse than a clean manual process.

What to automate and what to keep human

Automation follows scale and operating preference. Sunday does not impose it for its own sake. A 300-person company with one collection a year genuinely does not need HRIS-triggered credits. A distributed 5,000-person programme cannot survive without them.

Integrations belong to the store, the audience-facing layer. The internal side of the same programme, where a merch team manages inventory, users, campaigns and workflows, is the swag management platform. The two connect, and they are not the same thing.

To see how Sunday configures identity, funding and fulfilment together, explore the platform, the catalog, distribution and how it works.