Which SanMar interfaces do you use?

The ones your SanMar account is approved for. We confirm what is available with you during scoping rather than assuming a particular interface.

Is availability live?

No. Availability reflects what the supplier publishes at the cadence they publish it, and the cadence is agreed before build.

Can you set retail prices?

We apply your pricing rules. The rules themselves stay your decision.

Can this run alongside an ERP?

Yes. Whether the store or the ERP is the system of record for items and pricing is decided in scoping.

Supplier data · Apparel and promotional products

SanMar

Your store or ERP

Connect SanMar + Your store or ERP

Automate product and style data, cost and price data, availability, purchase order or order handoff, order acknowledgement and shipment detail between SanMar and Your store or ERP — with monitoring and managed support from APIWORX.

See How It Works

APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.

ERP + eCommerce Specialists

Managed & Monitored Integrations

Expert Integration Team

APIWORX Provides the Service

Yes. APIWORX connects SanMar to the store or ERP you already run.

But moving catalog files is only the beginning.

The work that actually costs you time is the process around the data: choosing what to list, applying your own pricing rules, keeping availability honest on the storefront, handing orders off cleanly and dealing with the lines the supplier cannot fill. APIWORX automates that whole loop and takes ownership of the exceptions.

Supplier collaboration Inventory synchronisation Order-to-cash automation

How it works

From requirements to a managed integration

Tell Us What You’re Connecting

Provide the systems, workflow and business requirements.

We Design the Integration

APIWORX recommends the integration architecture, mappings and implementation approach.

We Build, Monitor & Support It

APIWORX implements the integration and provides ongoing monitoring and support as applicable.

Who this is for

This page is for apparel and promotional-products businesses reselling SanMar goods who want catalog, availability and order handoffs to run without manual downloads.

What needs to be in place

An active SanMar account with integration access granted to you by SanMar.
A storefront or ERP that can accept product, price and availability updates.
An agreed decision on which SanMar styles, colours and sizes you actually list.
A named contact for pricing rules and substitution decisions.

When you may not need this

A short, stable range can be maintained by hand. Integration earns its place when the listed range is large, when pricing and availability change often, or when order handoffs are a daily manual task.

What is out of scope

APIWORX does not grant, negotiate or expand your SanMar account access; which interfaces are available is confirmed with SanMar and with you in scoping.
Your cost, margin and retail pricing rules stay yours; we apply the rules you set rather than deciding them.
Decoration, personalisation and production workflows sit outside this data flow.
Availability reflects what the supplier publishes at the cadence they publish it; this page does not promise live stock.

What actually moves, and who owns it

A representative scope. The exact interfaces available on your SanMar account are confirmed before build.

SanMarAPIWORX (mapping, retries, exception queue)Your store or ERP

Objects exchanged between SanMar and Your store or ERP, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Product and style data	SanMar	Store or ERP	SanMar	Agreed cadence	Previous values retained; changes reported	APIWORX
Cost and price data	SanMar	Store or ERP	SanMar for cost; you for retail	Agreed cadence	Held for review rather than published	APIWORX with your pricing owner
Availability	SanMar	Store or ERP	SanMar	Agreed cadence	Last known value retained; gap reported	APIWORX
Purchase order or order handoff	Store or ERP	SanMar	Your system	Order confirmed and eligible	Held in exception queue with the reason	APIWORX
Order acknowledgement and shipment detail	SanMar	Store or ERP	SanMar	As published	Retried, then queued for review	APIWORX

Three decisions that make or break this integration

The listed range is large and changes constantly

Style, colour and size combinations multiply quickly. Only the range you choose to list is synchronised, so retired items disappear and new ones appear without a manual audit.

Range selection maintained as configuration.
Discontinued items flagged rather than left live.
Attribute mapping kept consistent across the catalog.

Retail pricing must follow your own rules

Supplier cost is one input. Your markup, tier and customer-specific pricing rules are applied on the way through, and anything that would publish an unexpected price is held.

Cost and retail kept distinct.
Rule-based markups applied on write.
Out-of-range prices held for review.

An item is out of stock after the order is taken

Availability is published on a cadence, not continuously, so exceptions happen. They are surfaced with the order reference so someone can substitute or contact the customer.

Rejected or short lines queued with the reason.
Substitution decisions left to your team.
Recurring shortfalls reported as a range issue.

Reliability and ownership

The operating rules that apply to this workflow after go-live.

Every run is logged with the source record reference so a document can be traced end to end.
Failed messages are retried on a defined schedule; anything still failing lands in an exception queue rather than being dropped silently.
Duplicate prevention keys on the source system's own identifier so a replayed message does not create a second record.
Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
Mapping changes — new SKUs, new accounts, new locations, new partner requirements — are handled inside the ongoing engagement.
Support windows and response commitments live in your agreement; this page does not state an SLA.

How an item is traced

Illustrative — not customer data

An illustrative reference trace between supplier data and your own records.

How an item is traced
SanMar style and colour code	Your SKU
SanMar cost	Your retail price rule
Your order reference	Supplier order acknowledgement
Supplier shipment detail	Your order status

Scope and questions

Which SanMar interfaces do you use?: The ones your SanMar account is approved for. We confirm what is available with you during scoping rather than assuming a particular interface.
Is availability live?: No. Availability reflects what the supplier publishes at the cadence they publish it, and the cadence is agreed before build.
Can you set retail prices?: We apply your pricing rules. The rules themselves stay your decision.
Can this run alongside an ERP?: Yes. Whether the store or the ERP is the system of record for items and pricing is decided in scoping.