Skip to main content
Yes AI - AI Solutions Australia
For clothing and footwear brands running Apparel21 as their ERP and store system

Apparel21 Integration and Automation for Australian Fashion Brands

Apparel21 is built around the way fashion actually works: styles that come in colours and sizes, seasons that start and end, wholesale accounts alongside your own stores, and markdowns that move through a range in waves. That makes it a strong system of record. It also means the rest of your stack, your online store, your 3PL, your returns portal, your email platform, has to understand that structure, because most of those tools think in flat products and single SKUs.

This page is for brands that already run Apparel21, or are about to, and need it to talk properly to everything around it. It covers where the data should originate, how the style, colour and size matrix maps to a storefront, how store stock and online orders flow, how returns and exchanges should land back in the ERP, and where a partner connector already does the job well enough that a custom build would be wasted money.

Apparel21 Integration in Numbers

3 levels
Style, colour, size
The product hierarchy every connected system has to respect, even if it only stores the bottom level
Tens to hundreds
SKUs per style in a full size run
A single footwear style in eight colours and twelve sizes is ninety six sellable SKUs
Minutes, not hours
Sensible stock sync interval for fast sellers
The right interval depends on store count, order volume and API limits, so treat this as a target to test
1 owner
Per data field
Product, price, stock, customer and order fields each need one system that is allowed to change them

Four Things to Understand Before You Connect Apparel21

Most Apparel21 integration problems come from forcing a fashion data model into tools that were not designed for it, or from letting two systems both believe they own the same record.

The matrix is the product, not the SKU

In Apparel21 a style carries the description, season, category and imagery references, and the colour and size combinations underneath it carry barcodes, stock and sometimes price. Shopify thinks in products with up to a limited number of variants and options, which usually maps cleanly to style with colour and size options, but a style with many colours may need to be split into one storefront product per colour so each colourway gets its own page, images and search result. That decision affects URLs, reviews, collections and search, so make it once, deliberately, before any sync is built.

Apparel21 should own product, price and stock

For most brands the cleanest arrangement is that styles are created, priced and costed in Apparel21, and the storefront receives them. The storefront then owns presentation: long descriptions, imagery, SEO fields, collection placement. Problems start when merchandisers edit titles or prices directly in Shopify because it is faster, and the next sync either overwrites their work or is blocked by it. Decide which fields the integration writes and which it never touches, and tell the team.

The API exists, but it is not a free for all

Apparel21 exposes a retail API that integrators and partner apps use for products, stock, customers, orders and returns. Access is typically arranged through your Apparel21 account, the endpoints and capabilities depend on your version and licence, and call volumes need to be planned. A design that polls every SKU in the catalogue every minute will hit limits and slow the system for your stores. Good integrations request only what has changed, and batch the rest.

Your stores are part of the online offer

Brands with stores usually want online availability to include store stock, click and collect from a nearby store, and in store returns of online orders. Each of those needs Apparel21 store stock and transactions to reach the storefront quickly and accurately, plus rules about which stores are allowed to fulfil, how much stock to hold back for walk in customers, and what happens when the last unit in a store sells over the counter while an online order is in flight.

How an Apparel21 Integration Is Put Together

Six flows make up nearly every Apparel21 integration. The order matters: get product and stock right first, and orders, returns and marketing data become much simpler.

Storefront products built from Apparel21 styles

Style and product publishing

When a style is released for sale in Apparel21, the integration creates or updates the storefront product: style code, title, colour and size options, barcodes, retail price, compare at price where a markdown applies, season and category tags. The storefront team then adds or approves imagery and copy. A release flag or season status in Apparel21 should control what goes live, so a buyer can set up next season months ahead without it appearing online. Size sort order needs explicit handling, because alphabetic sorting puts 10 before 8 and XL before S.

Accurate sellable quantities online

Stock availability by location

Available to sell is not the same as stock on hand. It is on hand at the locations you allow to fulfil online, minus stock already allocated to open orders, minus any buffer you hold for stores or for damaged goods. The integration should calculate this per SKU and push only the SKUs that changed since the last run. For brands with many stores, publishing a per location figure lets the storefront offer click and collect accurately while a pooled figure drives the standard ship to home button.

Orders in Apparel21, ready to fulfil

Online order import

Paid orders flow into Apparel21 with the customer, delivery address, lines by barcode or SKU, discounts, shipping charge, gift cards used, payment method and GST. Decide whether discounts land as line level reductions or as a separate discount line, because that choice affects margin reporting by style. Orders should import once and only once, so the integration needs a record of which storefront order IDs have already landed, and it must handle edits and cancellations that happen after import.

Despatch confirmed back to the customer

Fulfilment and tracking

Whether you pick from your own warehouse, a 3PL or a store, the despatch event needs to reach the storefront with carrier and tracking number so the shipping notification goes out. If the 3PL or carrier platform has its own Apparel21 connector, check whether it writes despatch back to Apparel21, to the storefront, or to both. Split shipments, where part of an order comes from the warehouse and part from a store, need each parcel recorded against the right lines.

Stock and refunds that match

Returns and exchanges

Fashion return rates are high, so this flow matters more than in most categories. A return lodged through a returns portal, at a store counter or by post has to create a return in Apparel21 against the original sale, restock the item at the correct location in the correct condition, and trigger the refund, store credit or exchange in the storefront and payment platform. Exchanges for a different size are best handled as a return plus a new order linked together, so stock and revenue both stay honest.

One customer across stores and online

Customers, loyalty and marketing

Customers created online and in store should resolve to one Apparel21 customer record where possible, matched carefully on email and mobile rather than name. Purchase history from both channels then feeds your email and SMS platform and your loyalty program. Marketing consent must travel with the record and be honoured everywhere, consistent with the Spam Act 2003 and the Australian Privacy Principles, so an unsubscribe in one system is not undone by the next sync from another.

Common Apparel21 Integration Situations

TaskTraditionalDone ProperlyNotes
New season styles going onlineProducts keyed into Shopify by handCreated from released stylesStyle, options, barcodes and price come from Apparel21. Copy and imagery are added in the storefront and are never overwritten by the sync.
Last unit sells in storeOnline oversell and an apology emailAvailability updated within minutesStore sales reduce available to sell quickly, and a small per store buffer covers the gap between the counter sale and the next sync.
Mid season markdownPrices changed twice, in two systemsPrice change flows from Apparel21Sale price and compare at price set from the ERP, scheduled to start and end, so stores and online move together.
Online order returned in storeRefund issued, stock not movedReturn against the original saleThe store processes the return in Apparel21 against the online order, the item is restocked at that store, and the refund reaches the right payment method.
Size exchange by postRefund and hope they reorderLinked return and replacement orderThe replacement ships once the return is scanned, or earlier for trusted customers, with both legs visible on the customer record.
Selling on a marketplaceSeparate stock spreadsheet for the marketplaceSame available to sell figureMarketplace listings draw on the same calculation as the storefront, with their own buffer, and marketplace orders import like any other channel.
3PL takes over the warehouseDaily CSV emailed back and forthOrders out, despatch and receipts backPurchase order receipts at the 3PL update Apparel21 stock, and despatch confirmations close online orders. Partner connectors are checked first.
Wholesale account orders onlineRep types the order from an emailB2B order lands as a wholesale orderTrade customers order through a B2B storefront or portal at their price list, and the order arrives in Apparel21 as a wholesale order, not a retail sale.

Where Apparel21 Integrations Go Wrong

Two systems editing the same product fields

If both Apparel21 and the storefront can change titles, prices or tags, the sync becomes a tug of war and someone loses work every night. Write down which fields the integration owns, configure it to touch only those, and give the ecommerce team a clear place to make the edits they are allowed to make.

Full catalogue syncs on a timer

Pulling and pushing every SKU every few minutes is easy to build and expensive to run. It strains the Apparel21 API, slows stock updates when the catalogue grows and makes errors hard to find. Sync changes since the last successful run, and run a slower full comparison overnight to catch anything that was missed.

Barcodes that are missing, duplicated or reused

Barcodes are usually the join between Apparel21, the storefront, the 3PL and marketplaces. A size with no barcode, or an old barcode reused on a new style, breaks order import and stock updates for that line. Validate barcodes before a style is released online and refuse to publish a SKU without one.

Returns that skip the ERP

When the returns portal refunds the customer but nothing creates a return in Apparel21, stock never comes back on sale and sales figures stay overstated. Every return path, portal, store and post, needs to end in an Apparel21 return transaction, and a daily check should compare refunds issued against returns recorded.

GST and discounts that do not reconcile

Online prices are GST inclusive, discount codes may apply at order or line level, and gift cards are not a sale when they are redeemed. If the order lands in Apparel21 with discounts or gift cards treated differently from how your accountant expects, BAS reconciliation becomes a monthly exercise in guesswork. Agree the treatment with finance and test it on real orders.

Building custom where a partner connector fits

There are established partner integrations for Apparel21 covering common storefronts, 3PLs, carriers, returns and marketing tools. If one already covers your flows and your volumes, use it, and spend custom effort only on the gaps. A custom build is justified by genuinely unusual logic, not by a preference for owning the code.

How Yes AI Approaches Apparel21 Integration

A connector first assessment

We list every flow you need, check which ones an existing Apparel21 partner connector or app already handles well, and recommend those where they fit. You get a plain map of what to buy, what to configure and what genuinely needs building, before anyone writes code.

A field ownership map

For product, price, stock, customer, order and return data, we document which system owns each field and which direction it flows. This one document prevents most of the overwrites and duplicate records that cause Apparel21 integrations to lose trust.

Built, hosted and monitored by us

Where custom work is needed, the flows run on a managed cloud automation layer we operate, using the Apparel21 API through credentials you control. Every order, stock update and return is logged, and failures alert us before your customer service team hears about them.

Reconciliation that runs every day

Daily checks compare storefront orders with Apparel21 sales, refunds with returns, and published availability with Apparel21 stock. Exceptions arrive as a short list someone can act on, rather than a surprise at stocktake or BAS time.

How an Apparel21 Integration Project Runs

A typical project moves from discovery to live in weeks rather than months for standard flows, and longer when stores, wholesale and a 3PL all change at once. The timeline depends mostly on data quality and how many flows are in scope.

Map flows and data ownership

Workshops with merchandising, ecommerce, warehouse, stores and finance to list every flow, the system of record for each field, and the volumes and timing each one needs. We confirm your Apparel21 version, API access and any partner connectors already licensed.

Clean the product data

Audit styles, colours, sizes and barcodes for gaps, duplicates and inconsistent size naming. Agree the storefront product model, including whether colourways become separate pages. This step often takes longer than the build and pays off for years.

Build and configure

Configure partner connectors where they fit and build the remaining flows. Product and stock come first, then orders and fulfilment, then returns, customers and marketing data.

Test with real scenarios

Run real orders end to end: a markdown, a split shipment, a click and collect, an online return in store, a size exchange, a gift card redemption and a cancelled order. Finance checks the GST and discount treatment on actual transactions.

Go live and watch closely

Launch with reconciliation running daily and someone reviewing exceptions for the first few weeks, including the first markdown event and the first busy weekend. Then move to weekly reviews once the figures hold steady.

FAQ

Does Apparel21 integrate with Shopify?

Yes. Apparel21 has a retail API that partner connectors and custom integrations use to exchange products, stock, customers, orders and returns with Shopify and other storefronts. Several established partners offer Shopify connectors. The right choice depends on whether your needs are standard, such as products, stock and orders, or include store fulfilment, complex returns, wholesale and marketplaces that a packaged connector may not cover.

Should Apparel21 or Shopify be the source of truth for products?

For most fashion brands, Apparel21 should own the commercial data: style codes, options, barcodes, price, cost and season. The storefront should own presentation: long copy, imagery, SEO fields and collection placement. Splitting it this way means buyers and merchandisers work in the ERP while the ecommerce team keeps control of how products look online, and the integration never overwrites either side's work.

How often should stock sync between Apparel21 and the online store?

Often enough that a store sale or a 3PL adjustment reaches the storefront before the next customer can buy the same last unit. For many brands that means every few minutes for changed SKUs, plus an overnight full comparison. The right interval depends on order volume, store count and API capacity, so test it rather than assuming. A small buffer on low stock lines covers the gap between syncs.

Can online orders be returned in our stores?

Yes, and it is one of the most valued features for customers. It needs the online order to exist in Apparel21 so the store can process a return against it, a rule for which store the stock is returned to, and a refund path that reaches the original payment method or issues store credit. The integration then tells the storefront the order has been refunded so the customer record stays accurate.

Can Apparel21 handle wholesale orders from an online B2B portal?

Apparel21 supports wholesale as well as retail. Orders from a B2B storefront or portal can be imported as wholesale orders against the trade account, at that account's price list and terms, rather than as retail sales. Forward orders for a future season need their own handling, because they reserve future stock rather than current stock.

Do we need a custom integration or will a partner connector do?

Start with the partner connectors. If one covers your storefront, your 3PL and your returns platform at your volumes, it is usually cheaper and faster than a custom build, and it is maintained by someone else. Custom work makes sense for genuinely unusual logic, such as complex store fulfilment rules, multiple storefronts across brands or regions, or reconciliation and reporting no connector offers.

How do we handle GST, discounts and gift cards in Apparel21 orders?

Agree the treatment with your accountant before go live. Online prices are GST inclusive, so the order must carry the GST component correctly. Discounts can land as line reductions or a separate line, and the choice affects style margin reporting. Gift card sales are not revenue until redeemed, and redemption is a payment, not a discount. Test each case on real orders and check them against a draft BAS.

Make Apparel21 the Centre of Your Stack, Not an Island

Book a call. We review how Apparel21 connects to your storefront, stores, 3PL and marketing tools today, show you where data is being lost or overwritten, and recommend the simplest fix, including where a partner connector is the right answer.

All discussions held in confidence. Australian-based consultants.

Interactive controls are loading. Phone and email links are available.