Best Buy

An offer on their catalogue, not a second copy of it

Best Buy runs a shared catalogue: the product usually already exists and what you are adding is your offer against it. Sending a duplicate is rejected outright, so EasyeSuite works out which half to send before it sends anything.

Connecting

One API key, pasted once

Best Buy issues a single API key from its seller portal. Paste it in and the connection is made — there is no sign-in flow, no token to refresh and no expiry to diarise.

Sign-in: None — one pasted key
From: The Best Buy seller portal
Expiry: None
Fulfilment centres: Mapped to your warehouses

Worth knowing

A barcode they already hold is a rejection

Send a product whose barcode is already in Best Buy’s catalogue and the whole submission is refused, not merged. So EasyeSuite decides first: attach an offer to the catalogue product that exists, or send the product too when it genuinely does not. Once a match is found it is remembered, because a barcode can be held in a different form than the one you sent.

Duplicate barcode: Rejected outright
Offer against a match: Sent on its own
Resolved match: Remembered per item
Price: Travels on the offer

Limits

What it will not do

An order cannot be split across several parcels on Best Buy’s side — that is deliberately not claimed until multi-warehouse-per-order is confirmed with Mirakl.

A listing is one offer against one SKU, so a variant parent is refused rather than published.

Listings complete asynchronously: a submission is live when Best Buy finishes processing it, and failures come back as a report rather than an immediate error.

Everywhere else