Amrod: How AMROD cut a week of monthly SYSPRO work to a daily run in under a minute
AMROD is a South African supplier of promotional products, corporate gifts, clothing, headwear, and branded merchandise. Behind the catalogue sits a deeply custom technology stack. For nearly two decades a home-grown ERP has sat at the center of ordering, credits, approvals, warehouse links, website payment portals, and much of the financial work outside month-end. That control came with a cost: every integration change lived inside the core system.
“It makes the complex simple. Integration code is messy. Flowgear gives you a visual of what is actually happening. You can read it like a flow diagram and understand it in a few seconds.”
Every integration change meant another trip through the core ERP
AMROD's ERP combined data from surrounding systems and owned the integrations between them. Any change had to be built in that core, then pushed through a long development, QA, and regression cycle before release. For a business measured on time to market, that cycle was the bottleneck.
The team needed to decouple integration from the ERP so delivery could speed up without putting the systems that run the business at risk on every change. A recommended enterprise service bus during a 2016 warehouse project had already shown the other extreme: licensing in the millions per year. Building everything internally avoided that bill, but left AMROD maintaining heavy integration code itself.
Move integrations into Flowgear, including the path into Moyo
AMROD adopted Flowgear after its CTO raised the integration problem and was pointed at the platform. The direction from leadership is explicit: systems should not talk directly to each other. Integrations move into Flowgear one by one.
That same pattern is already part of Moyo, the next internal ERP now under design. Moyo means heartbeat in Swahili, and it is intended to replace the current ERP after roughly 19 years of accumulated development. Flowgear is not a side tool for the old stack. It is designed into the replacement.
A week of monthly finance work now runs daily in under a minute
One of the clearest early wins sits in international purchase order and GRV processing with SYSPRO. A finance team member used to spend about a week every month checking overseas receipts, creating GRVs against purchase orders, and manually posting the related records because SYSPRO could not automatically access the arrival data.
AMROD built the Flowgear workflow in less than a week. After QA and UAT, it runs daily in under a minute, closing POs from ERP and SYSPRO data and processing the financial records. Separately, a recent Moyo-related change that would have taken two to three weeks as custom code was stood up in Flowgear in about two days.
- International SYSPRO PO and GRV flow automated.
- About one person-week of monthly finance work reduced to a daily run under a minute.
- Workflow built in Flowgear in less than a week.
- Recent Moyo-related change: about two days in Flowgear vs two to three weeks custom.
- CTO mandate: no direct system-to-system integrations; Flowgear is the path.
Replace the ERP, keep the integration layer
AMROD's primary focus is still moving remaining integrations out of manual and custom paths into Flowgear while Moyo is built. The current ERP is estimated at about 19 years of development. Delivery is roughly aimed at the end of 2027, with additional squads being added to push harder. Flowgear is intended to carry both the current estate and the replacement.
More customer stories
Systems connected in this story
Could this be your integration story?
Start building free for 90 days, or book an Integration Assessment for a prioritized roadmap first.