Guide · Back Market sellers on InfiPlex
Back Market accepts roughly one in three refurbisher applicants and keeps measuring the ones it admits: return rate, defect rate, customer satisfaction, anonymous test orders, and, since January 1, 2022, a valid IMEI on every smartphone order, submitted up to 24 hours after ship. InfiPlex already pulls Back Market and Back Market Business orders, ties a serial or IMEI to every unit shipped, confirms tracking, and reprices toward the Buy Box hourly through its Back Market integration. An AI agent on the InfiPlex MCP server covers the questions a refurbisher used to answer by hand: which shipped phones have no IMEI yet, which serial went to which buyer, and whether the tracking send actually reached Back Market.
Why Back Market
A Back Market dispute is settled by evidence: which unit shipped, when, with what tracking. The IMEI and serial number guide explains why the seller with a clean record wins and the seller without one does not. InfiPlex holds that record on every order; the agent reads it back, finds the orders where it is still missing, and records it when a pack station key allows.
| What your team asks the agent | Tools it calls | What it hands back |
|---|---|---|
| "Which Back Market phones shipped today with no IMEI recorded?" | order_search on the Back Market channel with label_created_start_date today, then order_get per order |
Orders whose shipment lines carry no serial_number, with hours left in the 24-hour window |
| "What serial shipped on order BM-88213?" | order_search text_search on the marketplace number, order_get |
The serial or IMEI per unit, the package, the carrier, and the ship time, ready for the dispute reply |
| "Did every Back Market shipment from yesterday get tracking to Back Market?" | order_search with marketplace_fulfillment_error 1, then log_search on the Back Market send tracking types |
Orders Back Market rejected, with the error text from the log |
| "What is IP13-128-BLK-GOOD priced at, and when did it last change?" | price_get, price_search by modified date |
Current price and the recent changes, so an hourly repricer move is visible |
| "Which Business orders are open and how many units each?" | order_search on the Back Market Business channel, not fully shipped |
Bulk orders by size, oldest first, with the warehouse each routed to |
| "Did the Back Market order pull run in the last hour?" | log_search on the Back Market get orders types |
Last successful pull time, or the failed pull and its message |
Every tool above is documented on the tools reference. Submission mechanics for the IMEI itself are on the Back Market IMEI number management article.
IMEI and serials
InfiPlex records a serial per unit on the shipment: through the API in an automated flow, at the pack station by scan, or from a CSV of up to 5,000 serials loaded ahead of time. Back Market allows the IMEI up to 24 hours after ship. The gap that costs sellers is the unit that shipped with the serial step skipped. A shift lead on a warehouse key at 4 PM:
How a second tracking record on an already-shipped order is treated is an account-level question, so the agent shows the preview and lets the person decide rather than assuming. On an account where serials are assigned by API before ship, the question above returns zero orders and the agent says so.
Disputes
When a claim reaches Back Market's own support, the seller with the serial tied to the order has the evidence and the seller without it does not. The agent turns the lookup into a sentence a support rep can paste.
"Which order did serial 356938035643809 ship on?" The agent searches the orders in the claim window with order_search and reads shipment lines with order_get until it finds the serial, then returns the order, package, carrier, and ship time.
"What shipped on BM-88213?" order_search text_search finds the InfiPlex id from the marketplace number; order_get returns the units, each with its serial, and the tracking number Back Market received.
Back Market SKUs carry the grade. The agent reads the SKU on each line and pim_sku_get for the product record, so "was this sold as Good or Fair" is answered from what was actually listed.
order_note_create records the claim reference and resolution on the order, internal only, so the next person who opens it sees the history without the email thread.
Pricing
The Back Market repricer checks each enrolled SKU hourly against the Buy Box price and sets the SKU to the winning price when it is at or above your floor, otherwise to your regular price. The agent does not run the repricer; it shows you what it did and lets a person override.
A price change is a previewed write that propagates to every connected channel, so it sits behind the confirm gate described in how AI agent writes are protected. On a read-only key the agent explains and recommends.
Keys by role
The MCP server publishes a tool only when the key carries its scope, so the key is the whole permission model. Create each at Tools > Admin API on your instance with MCP Enabled, and send the URL and header from the set-up guide.
Read Orders, Read Inventory, Read Price, Read PIM, Read Log, Read Settings. Both MCP flags No. Every serial lookup, tracking check, and price question on this page works; nothing can change.
Add Write Orders. Tracking with serials stops at a preview the packer approves; notes and status write directly. Add Write Price only on a key held by whoever owns pricing.
Same scopes as the support key, used by an unattended agent from cron. The failed sync watch agent reports every failed Back Market tracking send each morning; a second job on the same pattern lists yesterday's shipments with no serial before the window closes.
Prompts
The agent reads the stored channel names from your order data rather than guessing them, so "Back Market" and "Business" in a prompt resolve to whatever your instance calls those two connections. More prompts by role are on the prompts page.
Frequently asked
The agent records the serial on the shipment with order_tracking_create, using serial_number on the line and save_items_as_qty_one so each unit is its own line. InfiPlex handles the submission to Back Market from that record, the same way a serial scanned at the pack station or assigned by API is handled. It is a previewed write on a key with Write Orders.
Only on a key with Write Price, and then behind a preview that shows the current and new price before anything propagates. If the SKU is enrolled in the repricer, the hourly run can move it again; the agent says so when it reads the repricer rule.
No; those are computed by Back Market. What the agent gives you is the InfiPlex record those outcomes rest on: what shipped, which unit, when, with what tracking, and whether Back Market accepted the send. That is the evidence that decides a dispute.
Yes. Back Market Business is its own connection on the instance, so order_source_eq on that channel name returns only the bulk B2B orders, and every tool on this page works the same way on them.
Everything that writes. Write tools are not published to a key without write scopes, so an agent on a read-only key has no tracking, price, note, or setting tool to call. It can read orders, inventory, prices, settings, and the log, which covers every lookup on this page.
No. The MCP server is included with API access on every InfiPlex plan. Keys are unlimited and MCP calls are not metered. Your AI vendor bills model usage.
Resources
We will connect an agent to a Back Market instance on a read-only key and pull the unit, serial, and tracking for that order, tool by tool.
Open Tools > Admin API, create a read-only key with MCP Enabled, and connect the assistant your team already uses. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Order ids, SKUs, serial numbers, prices, times, and warehouse names are examples. Back Market is a trademark of Back Market SAS. Model Context Protocol is an open standard.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License