Ottermerce

Bulk catalog import, export
and editing for BigCommerce

Sign in Start free

Help

Support

One person reads this inbox. You will get a human, not a queue number.

Request sent Thank you — it is in the inbox. Expect a reply within one business day, to the address you gave. Store-impacting issues are read first.
That did not send Something went wrong on our side, and your message was not delivered. Please try again, or email support@ottermerce.com directly.

Contact support

Everything except your name, email, topic and message is optional — but the optional fields are usually what turn two replies into one.

The number shown in the History URL.

Urgency

Pick the second one only if something is actively breaking a live store.

A results CSV, a screenshot or a small diagnostic file. Please do not attach your original catalog or customer file unless we ask for it.

Never send API tokens or passwords. Ottermerce support will never ask you to email an API token. If we need to see something in your store, we will ask you to run an export and send the result.

Prefer email? Write directly to support@ottermerce.com.
01 Before you write

The problems that come up most

Six answers that resolve most reports on their own. Open the one that matches.

A row failed and the message mentions several matches

The file identified a product by something that is not unique — a name, usually. Nothing is guessed, so the row fails and names the candidates. Add a Product ID or SKU column, or use the [ID] header suffix to pin matching to one column.

Every row failed with a permission error

The API token cannot reach the resource the file writes to. Run the file check first — it probes the one permission that file needs and tells you before anything is queued. In BigCommerce, create the token with modify scope for the relevant area.

An import is stuck at “processing”

An import finishes when its whole batch finishes, and a large file is many jobs. Give it time proportional to the row count. If it has genuinely stopped, send the import ID.

Images duplicated after a re-import

BigCommerce renames stored files, so matching by URL cannot work and images are matched by filename stem. Two different pictures whose source URLs end in the same basename look like one image. Use the Image ID column — our exports write it — to address a specific image exactly.

An update wiped a field I did not touch

It should not, and this is worth reporting with the file. A blank cell is treated as “absent” and is not sent, precisely so an empty column cannot erase stored values. The one documented exception is a variant SKU, which is always sent.

A category delete was refused

BigCommerce deletes a category's whole subtree without warning. A delete for a category that has children is refused unless the row sets Cascade to true, and the message says how many categories would go.

02 Requests

Feature requests, bugs, and the account

Both feature requests and bugs go through the same form — pick Feature request or Bug report as the topic and it is tagged for you. Feature requests that describe the problem rather than the solution get built more often, because they leave room for a better answer than the one you had in mind.

  • Change plan Send the form with topic Billing / plan. Plans are assigned by hand today, so there is no self-serve upgrade button to look for.
  • Delete your account Email from the account address and we will remove the account, its credentials, its files and its history within 30 days.
  • Disconnect a store Settings, in the app. This removes our copy of the token but does not revoke it — revoke it in BigCommerce.