Recurring Order #N tag now accurate for migrated subscriptions

Subi automatically tags each recurring order with a Recurring Order #N counter so merchants and their workflows always know where a subscriber stands in their cycle. For subscriptions migrated from other platforms (such as Skio), some contracts were receiving a tag one number higher than the correct count — for example, a second recurring order would be tagged Recurring Order #3 instead of Recurring Order #2.

Why it happened. When a subscription contract is migrated into Subi, the system records how many billing cycles were completed before migration and uses that offset to pick up the count where the customer left off. Shopify also associates those contracts with their original order from the source app. In some migrated contracts, that origin order was being included in the local order count and in the migration offset simultaneously — counting it twice and inflating the tag by one.

What changed. The tag calculation now correctly identifies the migration origin order and excludes it from the local order count. For migrated contracts that had no origin order synced, nothing changes. For non-migrated subscriptions, the logic is entirely untouched.

New recurring orders on affected contracts will now receive the accurate Recurring Order #N tag. Any merchant using these tags in Shopify automations, order management flows, or reporting will see correct values going forward.

If you use recurring-order tags in your Shopify flows or automations and migrated your subscriptions from another platform, this fix ensures the count matches the subscriber's actual history with your store.