Update
SHOPLINE joins the autonomous write lane — and connecting a second store stops deleting the first
TL;DR
Three things asked for, each of which turned out to rest on a defect. The headline is the autonomous lane, but the multi-store bug underneath it was the serious one — connecting a second store removed the first, with nothing to tell you.
What shipped
- Connecting a second store adds it alongside the first. Both commerce connect routes replaced every row for that platform, which is correct for platforms that return a complete account list and wrong for a paste-a-token flow carrying exactly one store.
- Reconnecting the same store refreshes it in place, so scheduled tasks and alert rules pointing at it stay alive.
- A write with no store named is refused, not guessed. With two stores connected, the previous behaviour fell back to whichever was first — a coin flip. It now refuses and names both so you can choose.
- SHOPLINE writes work on the autonomous lane, which previously covered Shopify but not SHOPLINE.
The wrong-store fallback exists on eight other ad-platform gateways with the same shape. Cross-provider it is safe — credentials resolvers reject an id from another provider — and within a provider it was fixed only for the two commerce lanes here.
Why the multi-store bug survived so long
The replace-everything behaviour is correct for connections where the provider hands back the complete list of accounts you can see — a row that is missing really has gone. Commerce connections are a different shape: you paste a token for one store. The same function served both, and the mismatch only becomes visible when someone connects a second store and loses the first.
Frequently asked questions
- Can I connect more than one Shopify or SHOPLINE store?
- Yes. Each store is added alongside the others, and reconnecting an existing store refreshes it in place so scheduled tasks and alerts that reference it keep working.
- What happens if I don't say which store to change?
- With more than one store connected, the write is refused and both stores are named so you can pick. Previously it silently used whichever happened to be first.
- Does this affect Shopify as well as SHOPLINE?
- Yes — the multi-store fix covers both commerce connect routes. The autonomous write lane is the part that was SHOPLINE-specific.