Apparel21 and Fontis Commerce Stack
What moves between AP21 and the stack
In an FCS build the integration layer is part of the platform rather than a connector bought to sit between two products. These are the flows it maintains, and the direction of each one is settled during design and written down.
Seasonal, Colour and Sized Products
Styles, colours, sizes and season data come out of AP21 into the catalogue the storefront reads, so what customers browse matches the product structure your merchandise planners work in.
Inventory and Availability
Warehouse and store stock reaches the storefront as an available-to-promise figure, calculated under allocation rules we agree with your team rather than published raw. The AP21 services page covers how we set those rules.
Orders and Fulfilment
Orders, payments and customer updates are written into AP21. Picking, dispatch, partial fulfilments and credits come back out as status the storefront shows, so finance is not reconciling two versions of the same order.
Customers and Loyalty
The AP21 customer record is the one the stack works from. Where you run loyalty in AP21, how online accrual and redemption connect to it is settled during design.
How Apparel21 connects to Fontis Commerce Stack
The integration layer sits between AP21 and the rest of the stack. AP21 does not push changes out, so the layer polls its Retail API on a schedule set per data type and keeps what the storefront needs ready to query: the product catalogue, the search index, availability figures and customer profiles. Pages are served from those, so the site runs at its own pace and AP21 handles integration traffic rather than requests from every shopper browsing a category page.
Orders, payment references, customer updates and returns travel the other way. They go into AP21 as queued operations with retries and reconciliation behind them, so a maintenance window means orders wait and drain when AP21 comes back rather than failing at checkout, and nothing lands twice.
Everything else in the stack connects through the same layer. Search, CMS, marketing and fulfilment systems take AP21 data by one documented route instead of each holding its own connection to the ERP, which is what keeps the number of integrations flat as you add tools.
What the rest of the stack does with it
AP21 is one system in an FCS build. These are the parts of the platform that sit around it, and what having them under one roof lets you do.
Enrichment Without ERP Changes
Editorial copy, lifestyle imagery, fit guides and campaign content live in a CMS or PIM and are composed onto AP21 product data at render time. Marketing can enrich a season's products without an ERP change request.
Search Indexed From AP21
Typesense or Algolia indexed from AP21 attributes and the availability figures the integration layer maintains, so search reads the same product structure and stock data as the rest of the storefront.
Store-Level Stock
AP21 already holds stock by store, and the integration layer can carry those figures through under explicit allocation rules. Which store-based fulfilment options they should support is worked out during scoping, against how your stores operate.
A Storefront Built Around Your Range
The storefront is custom-built rather than a theme, so what it can do is not limited by what a template system allows. Design, merchandising and page structure are yours to decide.
What varies between AP21 installations
AP21 deployments differ more than most ERPs. Your version, how it is hosted, and which modules you licence all affect which APIs are available and how much has to be handled around them. Some installations expose everything an integration needs through documented interfaces; others need scheduled extracts or a database-level read for particular flows. None of that is a problem, but it does change the scope, so we assess it before quoting rather than after.
The same applies to customisation. AP21 sites that have been trading for a decade usually carry local modifications, and those modifications are often where the business logic that matters actually lives. Finding them early is part of discovery. Coming in cold to an undocumented AP21 setup is ordinary work for us.
Apparel21 and FCS questions
What retail and technology leaders ask when they are scoping a composable build on top of AP21.
How is this different from your Shopify AP21 integration?
The Shopify AP21 integration connects AP21 to a Shopify store that owns the storefront and the commerce engine. This page describes AP21 behind Fontis Commerce Stack, where the storefront, search, content and integration layer are all yours to shape and AP21 is the operational system of record for the whole stack. Which one suits you depends on how much of the customer experience you need to control.
Does the storefront go down when AP21 does?
No. The storefront reads from indexes and caches the integration layer maintains, so browsing, search and product pages continue through an AP21 outage or maintenance window. Orders queue and drain when AP21 returns. What does go stale is availability data, so we agree up front how long that is acceptable and what the storefront should say once it is not.
Can we keep AP21 and still replatform the storefront?
Yes, and it is a common reason retailers come to us. AP21 tends to be the system nobody wants to touch, which makes it a good anchor for a replatform. The integration layer is designed against AP21 as it exists today, and the storefront is rebuilt around it.
What about POS and in-store trade?
In-store trade is recorded in AP21 against the same stock and customer records as online orders, so the integration layer works from one set of figures. What the storefront publishes from them is governed by the allocation rules you set.
Do we need a PIM as well as AP21?
Not always. AP21 holds the operational product data well, and a PIM earns its place when you have rich marketing content, multiple channels with different content requirements, or a supplier onboarding process that needs structure. We will tell you when a CMS alone will do the job.
Can you take over an AP21 integration someone else built?
Yes. We assess what exists, document what it does and where it breaks, then plan remediation or replacement. Migrations are staged so the cutover does not interrupt trade.
Ready to build in front of Apparel21?
Book a consultation and we will work through your AP21 setup, which data needs to reach customers and how quickly, and what the integration layer would have to carry.