Macy’s
Your offer on Macy’s catalogue
Macy’s runs a shared catalogue, so what you publish is usually an offer against a product that already exists. EasyeSuite resolves which half to send before sending it, and settles the payouts against the orders they belong to.
Macy’s syncs orders every five minutes, inventory every five minutes, pricing every ten minutes, returns hourly and payouts daily. Shipping methods are read from Macy’s and mapped to your carriers. Listings are submitted as a feed and tracked to completion.
Connecting
One API key, pasted once
Macy’s issues a single API key from its seller portal. Paste it in and the connection is made — no sign-in flow, no refresh, no expiry.
- Sign-in
- None — one pasted key
- From
- The Macy’s seller portal
- Expiry
- None
- Fulfilment centres
- Mapped to your warehouses
Worth knowing
Payouts arrive without a movement date
Macy’s payout rows carry no transaction date, so matching a payout by when the money moved cannot work — and a payout document is assigned days or weeks after the fact anyway. EasyeSuite follows the documents instead, reading each one whole and oldest first, so a half-settled payout is never recorded.
- Matched on
- The payout document
- Read
- Whole, oldest first
- Partial payouts
- Never recorded
- A backlog
- Drains across runs
Limits
What it will not do
An order cannot be split across several parcels on Macy’s side.
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 Macy’s finishes processing it.
Everywhere else
One catalogue, every channel you sell on
See Macy’s running against your own catalogue
A short walkthrough with our team, on your products and your orders rather than a demo workspace.