Start on schedule
appse ai runs the product synchronisation on your configured cycle without anyone starting it. New variants are picked up on the next pass rather than when someone remembers the catalogue needs updating.
Live webinar · 16 September 2026 · 11:30 AM CT: From Chat to Order: The WhatsApp Sales Agent for SAP Business One Save my Seat
About this template
A shirt in six sizes and four colours is one product to a shopper and twenty four item codes to the ERP. Bridging that means creating a configurable parent in Magento, creating every child variant, and attaching each one to the right parent in the right order. Done by hand it is slow, easy to duplicate, and the reason new variants sit unpublished for weeks. This template does it on a schedule and writes the result back.
Key benefits
Inside the flow
appse ai runs on a schedule, finds the child item in SAP Business One and prepares its product information in the structure Magento needs. It then checks whether the configurable parent already exists, creates it only when it does not, creates the child variant, and links the two into a configurable relationship. Once the link is established, appse ai writes the synchronisation result back to SAP Business One.
appse ai runs the product synchronisation on your configured cycle without anyone starting it. New variants are picked up on the next pass rather than when someone remembers the catalogue needs updating.
appse ai searches SAP Business One for the relevant child item and retrieves its product information using the item identifier. The ERP stays the source of truth for what the variant actually is.
appse ai selects the required fields and structures them consistently so they can be used to build the Magento product relationship. Consistent shaping here is what stops the storefront filling with variants that carry different attribute sets.
appse ai checks Magento for the configurable parent this variant belongs to. The answer decides whether a parent has to be created first or the workflow can go straight to the child.
Where no parent exists, appse ai creates it in Magento. Where one already exists, this step is skipped, which is what prevents a second parent being created for a product that already has one.
appse ai creates the child product from the prepared information so the variant is represented in Magento. Each size, colour or option combination becomes a real product record rather than a note on the parent.
appse ai attaches the child product to its configurable parent, completing the Magento product relationship. This is the step that makes the variant selectable on the storefront rather than a separate listing.
Once the relationship is established, appse ai updates SAP Business One with the synchronisation information. Anyone in the ERP can see that the item has been published and linked, without checking Magento.
Keep Magento configurable products in step with SAP Business One item data, parent and child, on a repeating schedule.
01
Scheduled processing keeps the parent and child structure moving, so the team stops maintaining Magento relationships by hand.
02
Child products are created and attached to the correct configurable parent, which is what a shopper needs to select a size or colour on one page.
03
The existence check runs before creation, so a product that already has a configurable parent does not get a second one.
04
Product data is prepared and transferred through one repeatable path rather than re-entered each time a new variant appears.
05
The completed relationship is written back to SAP Business One, so the publication status is visible where the item lives.
06
A scheduled, repeatable process handles ongoing additions to a variant heavy catalogue without a matching increase in manual work.
07
A new variant becomes a linked, selectable option on the next scheduled run rather than waiting for a catalogue update session.
01
Scheduled processing keeps the parent and child structure moving, so the team stops maintaining Magento relationships by hand.
02
Child products are created and attached to the correct configurable parent, which is what a shopper needs to select a size or colour on one page.
03
The existence check runs before creation, so a product that already has a configurable parent does not get a second one.
04
Product data is prepared and transferred through one repeatable path rather than re-entered each time a new variant appears.
05
The completed relationship is written back to SAP Business One, so the publication status is visible where the item lives.
06
A scheduled, repeatable process handles ongoing additions to a variant heavy catalogue without a matching increase in manual work.
07
A new variant becomes a linked, selectable option on the next scheduled run rather than waiting for a catalogue update session.
Keep exploring
Every repetitive process between your ERP, CRM, and business apps has a template. Find yours, customize it, and go live today.
Customize the flow
Every trigger and action this template uses is available in the appse ai builder, so the same flow can be rebuilt with your own routing, thresholds and destinations.
Questions & answers
Everything you need to know about this template before you deploy it.
Discover how appse ai has helped businesses automate processes and achieve growth through our users' success stories.
Start free — no credit card, no setup calls required. Use this template as-is or customize every step inside the appse ai no-code builder and go live today.