Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Trade item numbers, pack levels and the attributes held against them arrive in Shopify from GS1 data, so a listing carries exactly the identifier the rest of the supply chain already uses.
GS1 numbers identify a trade item at a packaging level, which means a single each, an inner and an outer case each have their own number and their own attributes. Shopify sells one thing at a time. Left to a manual process, whoever builds the listing picks whichever number was on the spreadsheet, so a shopper buys an each and a case turns up, or a marketplace rejects the listing because the identifier describes a pallet. Connecting GS1 and Shopify makes the packaging level an explicit decision, so the number on the listing is the number of the thing being sold.
DATA THAT FLOWS BETWEEN THEM
Trade item numbers
Packaging levels
Brand and product names
Net content
Product variants
Barcode fields
Each GS1 packaging level is mapped deliberately, so the Shopify variant a shopper buys carries the identifier for that unit rather than for the case it was shipped in.
Alumio connects to the GS1 data you hold through its available API, as it would any reachable system, so identifiers and attributes reach Shopify without a spreadsheet in between.
Because the identifier on the Shopify variant matches the one the supply chain uses, a return, a recall or a marketplace feed can all point at the same physical item.
Net content and pack detail travel with the number, so a listing describes what is in the box and a customer comparing two sellers is comparing the same quantity.
Alumio reads trade item numbers with their packaging levels and writes the one you nominate onto the matching Shopify variant, so a multipack and a single are separate variants with separate identifiers rather than one guess.
The identifier reaching Shopify is the one printed on the unit being sold, so a warehouse scan, a marketplace feed and a customer return all resolve to the same item instead of to a pack level that nobody actually shipped.
Brand, product name and net content arrive from the GS1 data alongside the number, so a listing is built from the attributes the manufacturer published rather than from whatever the last person to touch it typed.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
Who is upstream of you decides the next connection, and for product data it is usually whoever prepares the images. GS1 data gives Shopify the identifier and the measurable facts and says nothing about how the product looks, so the retouching and asset preparation service is the common addition. Alumio holds both connections, so the picture and the number reach the same Shopify variant rather than arriving through two different people.
The identifier comes first and everything else hangs off it. Alumio reads GS1 trade item numbers with their packaging levels and attributes, matches them to Shopify variants on the identifier you nominate, and writes the attributes you choose. Levels you have decided not to sell are read and ignored, so a case never quietly becomes a purchasable variant.
No, because the standard has already done most of the work. GS1 attributes arrive in defined fields with defined meanings, so mapping them onto Shopify is a matter of saying which goes where rather than interpreting anybody's local convention. Where a business has extended its own product data beyond the standard, custom logic remains available through the Code Transformer for those fields alone.
The one you actually sell, which is a decision rather than a default. GS1 numbers identify a trade item at a packaging level, so an each, an inner and a case are three numbers describing three different things, and only one of them is what a Shopify shopper receives. Mapping the level you sell to the variant, and leaving the others out, is what keeps the barcode on the parcel matching the listing.
An identifier that changed underneath the listing is the failure to catch, because everything downstream is keyed on it. The GS1 number, the Shopify variant and the reason are all recorded; alerting is immediate, retries automatic where configured, and per-route no-activity alerts mean a silent stop is still reported. The previous value stays live, so no listing points at nothing.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
