No replatforming. No data exports. No developer on retainer. The manufacturer's catalogue is mirrored once, and the jeweller pastes a single script tag on the page where they want it to appear.
We do the connecting. The jeweller does the pasting. After that it runs itself.
We map the manufacturer's product structure into the Ring-Sync pipeline — profiles, metals, patterns and stones — as a single source of truth.
The jeweller drops one script tag on their wedding-rings page. Theme, header and checkout stay exactly as they are.
<script src="…/inject/plain.js" data-client="you"></script>
Prices follow the live metal market daily; any catalogue change the manufacturer makes propagates to every storefront automatically.
One tag renders one surface. Want all three on a page? Three tags, same data-client — the engine, styles and catalogue load once and are shared.
The integration is designed so neither party takes on a project — just a connection on one side and a paste on the other.
Your product data is mapped a single time and becomes the source of truth for every stockist who switches Ring-Sync on.
It runs inside your existing site — Shopify, WordPress, bespoke, anything that renders HTML. Nothing else changes.
The widget is a good guest — isolated, cached and theme-agnostic.
Every rule is namespaced under .rsync-root, so the widget can't leak into — or be broken by — the host theme.
Multiple surfaces on a page share a single engine, stylesheet and catalogue fetch — the page stays fast.
Dawn, Horizon or bespoke — the add-to-cart tries several strategies and the badge ticks up whichever theme is live.
Runtime files are served with cache headers and CORS, so loads are quick and the same build serves every client.
Improve the widget centrally and every client's page picks it up on next load — no action needed from the jeweller.
If the spot-price feed is briefly unreachable, the widget falls back to a sensible price rather than breaking the page.
No. Ring-Sync runs inside your current site as a script tag. If your page can render HTML, it can host the widget — Shopify, WordPress, Squarespace or bespoke.
Styles are namespaced under .rsync-root so they don't leak into your theme. In the rare case a very high-specificity theme rule interferes, it's a quick CSS tweak on our side.
Your choice: native Shopify add-to-cart, a server-priced draft order, or a booking enquiry for appointment-led jewellers. It's a config setting, not a code change.
We do. Improvements ship centrally and your page picks them up automatically. The manufacturer's catalogue edits propagate the same way — you do nothing.
See the snippet rendered on a neutral host page, then we'll have you live on your own storefront within a day.