Does StoreTwin work with Arigato Automation?
Mostly yes, with one honest boundary: StoreTwin syncs whatever Arigato Automation writes into your source store - tags, fields, metafields - and delivered them in about twelve seconds in our test. What does not work is an Arigato rule in the receiving store that adds its own tags: StoreTwin's repair compares the full tag set against the source and removes tags the source does not have, so the rule's tag does not survive the next check. Both behaviours below were verified by running both apps on two development stores on 30 August 2026, not by reading documentation.
We are not affiliated with Arigato or its developer Bonify. This page describes what happened when both apps ran on the same pair of stores.
What works: Arigato writes in the source store
This is the setup that behaves exactly as both apps intend. Arigato runs its automation in the store that owns the catalogue - tagging by price point, rewriting fields, maintaining metafields. StoreTwin treats those writes like any other edit in the source store: the next check names the difference, and if syncing is on, delivers it to the receiving store.
In the test, an Arigato bulk workflow added a tag to products in the source store. The webhooks reached StoreTwin within seconds, the check named the tag difference on each linked product, and the write landed in the receiving store about twelve seconds after the workflow ran. Removing the tag later propagated the same way.
One plan-dependent detail: on the free plan StoreTwin repairs only the products you picked, so Arigato's changes on unpicked products stay in the report as named differences and are not copied. That is the free plan working as designed, not an incompatibility.
What does not work: an Arigato tag rule in the receiving store
The tempting setup is a rule in the receiving store that reacts to a delivered tag with local merchandising - "when a product gets tag X, add tag local-merch". We built exactly that rule and watched it fight the sync:
| 1 | StoreTwin delivers the source tag - the receiving product is updated |
| 2 | The Arigato rule fires and adds its own tag in the receiving store |
| 3 | StoreTwin's next check compares full tag sets, sees a tag the source does not have, and removes it |
| 4 | The rule fires again - and after a couple of rounds Arigato's own re-entry protection stops it |
In our run this converged after three repairs in thirty-five seconds: no infinite loop, both apps' safety rails held. But the outcome is that the rule's tag is gone - the source's tag set wins every time. If your merchandising depends on that local tag surviving, this setup does not work, and no configuration of either app changes that: it follows from StoreTwin syncing tags as a complete set, one way.
The compatible way to react in the receiving store
React to the delivered tag with things StoreTwin does not sync. StoreTwin never touches collection membership, prices after the product is first created, or the receiving store's own theme and merchandising surfaces. So:
- an automated collection in the receiving store whose condition is the delivered tag - products flow in and out as tags arrive, and nothing fights the sync;
- price rules or discounts in the receiving store keyed to the delivered tag - StoreTwin sets a price once at creation and never moves it afterwards;
- theme sections and filters that read the delivered tag.
The rule of thumb: in the receiving store, read the synced fields as much as you like, and write only to surfaces the sync does not manage. What the app syncs and what it leaves alone is listed on what sync apps can and cannot do.
If you run both apps
- Put Arigato's catalogue automation in the source store.
- In the receiving store, avoid rules that write to synced fields - tags, titles, descriptions, synced metafields. They will be overwritten, reported as differences, or both.
- Watch the connection page after setting up a new rule: if the same product keeps being rewritten, StoreTwin names it there - that is the repair-loop detector doing its job.
Tested 30 August 2026 with Arigato Automation by Bonify installed on two Shopify development stores alongside StoreTwin. App behaviour changes with releases; if you see something different, tell us at support@storetwin.app and we will re-run the test. Comparing sync apps themselves: the category compared.
The free plan audits a catalogue of any size - including one your automations are writing to - and names every difference by product and field.