Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
A drawing revision published to a WooCommerce page decides what a customer is actually buying, so the dimensions on screen and the geometry SolidWorks holds stop drifting apart between releases.
An engineered part is defined by its drawing, and the drawing has a revision. A WooCommerce page showing dimensions and a diagram is describing one particular revision of it, and when engineering issues the next one the page carries on selling the old shape. So an order arrives against a spec that no longer exists, the workshop makes the current revision, and the customer receives something that does not match what they were shown. Connecting WooCommerce and SolidWorks ties the page to the revision, so what is published and what is manufactured are the same thing.
DATA THAT FLOWS BETWEEN THEM
Part numbers
Drawing revisions
Dimensions
Material specifications
Product records
Configuration options
The drawing revision a WooCommerce page describes is the one SolidWorks currently holds, so a customer ordering from published dimensions gets the part that is actually made.
When engineering issues a revision, the page follows on the schedule you set, so an order is never taken against a specification that was superseded three weeks earlier.
Dimensions and material detail come from the model rather than being retyped, which removes the transcription error that only shows up when a part arrives and does not fit.
Engineering stops proofreading the website, because every page is built from the drawing record itself rather than from a written summary that somebody made once.
Alumio connects to SolidWorks through its available API, as it would any reachable system, and writes the current revision, its dimensions and its material detail onto the matching WooCommerce product record each time.
A new revision issued in SolidWorks updates the WooCommerce page on the schedule you choose, so the diagram and the figures a customer reads move when the drawing moves rather than at the next scheduled content review.
Where a revision changes the part enough that the old one should not be bought, the WooCommerce product is withdrawn rather than quietly updated, so nobody can order a shape the workshop has already stopped making.
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.
What the drawing turns into is the useful question, and for a website it turns into something a customer can look at. A 3D asset and viewer service is the common addition, because SolidWorks holds the model and a WooCommerce page needs something a browser can spin, which is a different file. Alumio holds both connections, so the viewer and the dimensions on the page come from the same revision.
The revision is the trigger, and everything else follows from it. Alumio reads the current SolidWorks revision for the parts you nominate and writes its dimensions and material detail to the matching WooCommerce product on the schedule you set. A revision still in progress is not published, so a page never shows a shape that has not been released.
No. The revision being the trigger is a setting rather than logic somebody maintains: which SolidWorks parts are in scope, which fields reach the WooCommerce product, and whether a new revision updates the page or withdraws it. Because engineering data carries local convention in how revisions are named, the Code Transformer stays available for reading one that will not sort as it stands.
Whichever one it was last given, which is the problem when nobody is watching. A WooCommerce page carries dimensions and a diagram from one particular SolidWorks revision, and a page is not updated by a drawing being issued, so the honest answer is either the current revision or an old one, and the business gets to choose which by deciding what a new revision does to the page.
Retries run where configured, an alert fires as soon as WooCommerce will not take an update, and the revision Alumio read from SolidWorks is recorded with the reason it failed. The drawing revision that lagged is the failure this catches, because a page showing superseded dimensions looks entirely healthy, so unresolved parts stay listed and nothing is published quietly from an old model.
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)
