BigCommerce store panel

Connecting a sales channel means signing in to that marketplace from the same browser that holds the store panel. Two channels for two seller accounts mean two sign ins that should never share one.

From that moment the marketplace sees the device and the address behind both, which is how two seller accounts become one to it.

The panel gives each person their own user with their own permissions, and a shared login throws that distinction away. It also empties the history of changes, because every change carries the same author.

A profile per person keeps the sessions apart on the machine, so the permissions stay where they were set. A person who leaves then loses one profile instead of a password three people already know.

Product work that reaches a connected channel is counted twice: once by the store and once by the marketplace at the other end. The marketplace count is the stricter of the two and it is not ours to raise.

A counter warns partway and keeps showing the number, so the second count never arrives as a surprise. It does not stop you.

A store connected this week starts at a fifth of the daily ceiling and reaches the full number on the seventh day. A channel connected on the third day inherits that day's number rather than starting a count of its own.

The ramp is a fraction of the scenario ceiling, so the pace of the channels behind it rises with it.

A sandbox store and the live store are different accounts holding different data, and one browser is all it takes to confuse them. The panels look alike, which is exactly why the mistake is made at speed.

A profile each makes them two browsers, and a test order can no longer land where the real orders are.

The terms of service cover the store, and every connected channel adds the rules of the marketplace on its own side. The store terms change on one schedule and each channel on its own.

Read each at the source, because a channel can be disconnected by either end. We link them instead of retelling them.