Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Web sales reach Sage 100cloud inside the period they belong to, so a month does not close and then quietly acquire revenue from an order that turned up two days after the month had already ended.
Sage 100cloud closes periods, and once a period is closed an entry cannot simply be added to it. A WooCommerce shop trades through the night and over weekends, so orders keep arriving after the accountant has drawn a line, and each one has to land either in the month it was placed or in the month it was noticed. Left unmanaged the two months both look slightly wrong, and the comparison a business runs against last year is quietly on a different basis. Connecting WooCommerce and Sage 100cloud makes that a rule rather than a habit that changes with whoever is closing the month.
DATA THAT FLOWS BETWEEN THEM
Web orders
Order lines
Posting dates
Sales invoices
Customer records
Shipping charges
An order's posting date is decided when the route is configured, so revenue lands in the period the sale happened in rather than the one the integration ran in.
An order arriving after a Sage 100cloud period has closed is held and reported rather than forced into the next month without anybody being told that it had moved at all.
Because every order posts on the same rule, a year-on-year comparison is on one basis instead of quietly shifting with whenever the period close happened to fall.
Shipping charged and shipping paid both reach the ledger, so the margin on a web sale includes the cost of getting it there rather than only the revenue it brought in.
Alumio posts each WooCommerce order into Sage 100cloud against the date rule you set, so a sale placed at eleven at night on the last day of the month lands in that month and not in the one the integration happened to run in.
Alumio connects to Sage 100cloud through its available API, as it would any reachable system, and holds an order whose period has already closed rather than posting it to the following one in silence and hoping nobody checks.
Shipping charges and the carrier cost both reach the ledger against the order, so the figure a business looks at for web margin is not revenue with the cost of delivery quietly missing from the figure entirely.
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.
Which cost is missing from the margin is the question that opens the next connection, and on a web sale it is usually the freight. A shipping cost audit tool is the common addition, because WooCommerce records what the customer paid for delivery and Sage 100cloud records the carrier invoice, and the gap between them is a real number nobody owns. Alumio holds both connections, so the two meet on the order.
The posting period is settled first, because everything downstream depends on it. Alumio reads WooCommerce orders on the schedule you set and posts them into Sage 100cloud against the date rule you chose, holding anything whose period has closed. Customer records are matched rather than created afresh, so a repeat buyer does not accumulate accounts.
No, and the boundary that matters is the period rather than the field mapping. Which WooCommerce date decides the posting period, what happens to an order that arrives after a close, and which Sage 100cloud accounts receive the shipping figures are settings in Alumio's interface. Where a business runs an unusual cut-off, the Code Transformer takes that rule and the rest stays configuration.
The one the sale happened in, if you decide that before the first close rather than after it. Sage 100cloud will not accept an entry into a closed period, so a WooCommerce order arriving late has to go somewhere, and defaulting it into the current month moves revenue between periods without a record. Holding it and reporting it means somebody chooses, and the choice is visible.
The period closed early on somebody, which is when this hurts, because the entry then has nowhere correct to go. Alumio catches the refusal as it happens and holds an order whose period has closed rather than posting it forward, records what it read from WooCommerce, alerts at once naming the order and the reason Sage 100cloud refused it, retries where configured, and keeps it listed until a person decides, so nothing moves month quietly.
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)
