Platform coverage
Which storefront platforms each product supports today, how it installs, what it reads and what it is allowed to write back.
| Platform | YourSizer · sizing | ResReturn · returns | NoShot · publishing |
|---|---|---|---|
| Shopify | Live | Live | Live |
| ikas | Live | Live | Planned |
| Ticimax | Live | Live | Planned |
| T-Soft | Live | Early access | Planned |
| IdeaSoft | Live | Planned | Planned |
| Faprika | Live | Planned | Planned |
| WooCommerce | Planned | Planned | Planned |
| Custom storefront | Live | Planned | Early access |
Live — running in production on merchant storesEarly access — built and verified, enabled merchant by merchantPlanned — on the roadmap
What the three states actually mean
Live — running in production on a merchant’s own store. Early access — built and verified end to end, being enabled merchant by merchant. Planned — on the roadmap, same integration contract.
A platform with working code but no merchant running it yet is in early access, not live. We would rather tell you that up front than during onboarding. Any store not listed here can still run the YourSizer widget with the loader script tag.
Per-platform integration
Shopify
- Install
- App install with OAuth. The sizing widget and the return entry point are added as theme app embeds — no theme code editing for the standard case.
- What syncs
- Products, variants, size options, orders with line items, fulfilments and delivery events, refunds.
- What we write back
- Refunds, exchanges, store credit (with an optional merchant bonus), and (NoShot) product media appended to the catalogue. Writing stock back requires the inventory permission to be granted at install.
- Notes
- YourSizer is listed on the Shopify App Store as “YourSizer”. The ResReturn app is in App Store review; until it is listed, stores are set up through a demo or early-access link. The return portal can also be served from the merchant’s own domain through an app proxy, so the shopper never leaves the store. Data-deletion and uninstall compliance webhooks are handled.
ikas
- Install
- OAuth app connection. The sizing widget’s storefront script is installed for you and reinstalls itself if it goes missing; a small storefront script also routes the native return entry point into the ResReturn portal.
- What syncs
- Products and variants, orders and line items, order status transitions, delivery state.
- What we write back
- Refunds, partial refunds, store credit as a readable coupon code.
- Notes
- Storefront overrides are applied through the theme’s script slot, so the portal link replaces the platform’s built-in return action. Storefront changes take a few minutes to clear cache.
Ticimax
- Install
- Web service credentials plus a product-page script block. The widget reads the product’s variant model from the page and maps size options to the store’s own selectors.
- What syncs
- Products, size and colour variants, orders and lines, order status.
- What we write back
- Return requests, refund and cancellation actions, and store credit as store points (Para Puan).
- Notes
- Sizing has been in production on Ticimax stores for some time, and returns now run live as well. Store credit is added to the shopper’s store points balance at a rate the merchant sets in the panel. On themes where the storefront loader is fixed, widget behaviour is configured on the bundle side rather than in the page snippet.
T-Soft
- Install
- REST integration with token authentication issued from the store’s admin.
- What syncs
- Products, orders and order lines with per-line sizes.
- What we write back
- Return requests and refund actions (ResReturn, early access).
- Notes
- Tokens are short-lived and refreshed by the adapter. Webhook support is still being finalised, so order state is reconciled on a schedule as well as on demand.
IdeaSoft
- Install
- OAuth connection from the store admin.
- What syncs
- Catalogue with category tree, orders and line items, per-garment sizes.
- What we write back
- ResReturn write-back (per-line refund requests) is planned.
- Notes
- Verified end to end against a live store, including partial returns where only some lines of an order come back. Categories are resolved from the catalogue tree rather than from the product title.
Faprika
- Install
- API credentials from the store admin plus the storefront script.
- What syncs
- Products, orders and lines, per-garment sizes, existing returns.
- What we write back
- ResReturn write-back (return records and refund actions) is planned.
- Notes
- Verified on more than one store, including a non-apparel catalogue, to confirm the integration does not assume fashion-shaped data.
WooCommerce
- Install
- Native integration coming soon. Until it ships, the YourSizer widget runs on a WooCommerce store with the loader script tag, like any custom storefront.
- What syncs
- Planned — the same integration contract as the platforms above.
- What we write back
- Planned.
- Notes
- Listed so you do not have to ask: it is not live yet.
Custom storefront
- Install
- One loader script tag, copied from the merchant panel, for the sizing widget. For returns, a hosted portal with an API and webhooks is planned.
- What syncs
- Whatever you send us — a product feed and an order feed are enough to start.
- What we write back
- Nothing for sizing. For returns, refund and stock actions will be executed by your systems on our webhook, since there is no platform API for us to call.
- Notes
- This is the path for bespoke platforms. The cart-to-order signal chain has to be wired explicitly, because there is no platform-provided cart token to rely on.
How we add a platform
A platform is not “integrated” when the code compiles. It is integrated when it has been run end to end against a real store.
Authenticate. OAuth or token auth against a live store, including token refresh and revocation.
Sync the catalogue. Products, variants, the category tree and the size options — with the category resolved from the tree, not from the product title.
Sync orders. Orders with line items, per-line sizes, delivery events and existing returns. Delivery is what anchors the return window.
Create a return. Including a partial return where only some lines come back, then confirm it on the platform side.
Execute an outcome. Refund, store credit, exchange — then verify the money actually moved on the platform, not just in our own log.
Make failures loud. Any swallowed error that could let a broken integration look healthy is turned into an explicit, logged skip with a reason.