Explore AIMS360's apparel business software
FREE DEMO

Bloomingdale's runs on the same Macy's, Inc. vendor standards for bulk and dropship, then diverges at the marketplace with its own Mirakl storefront, weekly settlement and returns handling. AIMS360 runs wholesale, Vendor Direct Fulfillment and marketplace from one available to sell pool.

Luxury size-color inventory matrix synced to Bloomingdale’s in AIMS360 ERP
Bloomingdale's EDI integration

Bloomingdale's EDI and marketplace, one system

Bloomingdale's runs on the same vendor standards as Macy's for bulk and dropship, then diverges completely at the marketplace. AIMS360 handles both: 850 purchase orders in, 856 ASNs with GS1-128 carton labels, 810 invoices and the 832 UPC catalog out, plus the separate Mirakl storefront, all drawing on one available to sell pool. Built for the designer and fine jewelry floor, where a single unit is worth getting right.

AIMS360
Consumer brands ERP · native Bloomingdale's EDI
1 standard
Shared with Macy's for bulk and dropship
Own store
Separate Mirakl marketplace and terms
3 entities
Bloomingdale's, the Outlet, and the marketplace
350+
Retailers via native EDI
The short answer

Bloomingdale's runs on the Macy's vendor standards

For bulk wholesale and dropship, Bloomingdale's is not a separate integration. The Macy's, Inc. Vendor Standards state that the term Macy's refers to all entities affiliated with Macy's, Inc., including those that operate Bloomingdale's, macys.com, bloomingdales.com and the Bloomingdale's Outlet Stores. One portal at MacysNet, one standards document, one UPC catalog provider, one dropship program. Macy's Backstage is the carve out with its own standards, not Bloomingdale's.

That is genuinely useful if you already sell one banner. A brand set up for Macy's is substantially set up for Bloomingdale's, and the shared 856 test and audit request form even runs by division across Macy's, Bloomingdale's, Bloomingdale's Outlet and Backstage. The full requirement detail, the document set, the GS1-128 label spec, floor ready, RFID, onboarding weeks and expense offsets, is on the Macy's EDI page and applies here without change.

What is not shared is the part most brands underestimate: the marketplace, the buying organization and the merchandising expectations of a designer floor.

Where it differs

Three things Bloomingdale's does its own way

Its own marketplace Bloomingdale's runs a separate Mirakl storefront from Macy's Marketplace, with its own onboarding, its own commission structure, weekly settlement rather than twice monthly, and Bloomingdale's supplying return labels which are then charged back to the merchant's carrier account. Being live on Macy's Marketplace does not put you on Bloomingdale's.
Its own vendor entities Bloomingdale's and Bloomingdale's Outlet are named as distinct vendor entities in Macy's onboarding documentation, with their own contacts and their own setup, even though the standards they follow are the same. Treat the Outlet as a separate account, not a channel.
Its own buying Bloomingdale's is a designer and luxury floor with a different assortment strategy from Macy's. The marketplace reflects this: Mirakl describes Bloomingdale's running three distinct models, e-concession for luxury brands that want full control of their own assortment, complementary assortment for long tail SKUs, and incubation for emerging brands.
Dropship is identical to Macy's. The Vendor Direct Fulfillment standards read Macy's and Bloomingdale's throughout, use the same operations contact, and offer the same two connection paths: direct EDI using the Vendor Direct mapping variants, or the Rithum and CommerceHub OrderStream connection. There is no separate Bloomingdale's dropship platform or portal.
Marketplace and e-concession

Wholesale, dropship and marketplace are three different relationships

They look similar from the outside and behave nothing alike once you are running them.

01

Bulk wholesale

Bloomingdale's buys the units. A purchase order arrives as an 850, you ship floor ready to a distribution center or direct to store with GS1-128 carton labels, and you invoice on an 810. After receipt the inventory is theirs and your availability stops mattering.

02

Vendor Direct Fulfillment

You hold the stock. Single customer orders arrive, the complete order ships to the shopper within two business days with a Bloomingdale's branded packing list in the carton, and you accept the consumer return. Availability publishes by EDI 846, once per business day unless approved for more. Vendors are reviewed monthly against Federal Trade Commission performance benchmarks.

03

Bloomingdale's Marketplace

Mirakl powered, and a different commercial relationship entirely. You are the seller and shipper of record for the merchandise, Bloomingdale's collects payment from the shopper and remits net of commission. Integration is by Mirakl API, CSV feed or EDI through a Mirakl Connect account, on its own catalog and its own taxonomy.

04

E-concession

A model inside the marketplace rather than a separate integration. Aimed at luxury brands that want to control their own assortment, pricing presentation and stock on the Bloomingdale's storefront rather than hand it to a buyer. Operationally it is still a Mirakl connection, so it draws on the same inventory feed as everything else you publish there.

None of them share inventory, and that is the whole problem

VDF publishes availability through EDI 846 on Macy's cadence. The marketplace publishes through Mirakl on Mirakl's cadence. Neither reserves stock on the other's behalf, and a bulk purchase order draws down the same physical units without telling either one. Add Macy's alongside Bloomingdale's and you have four or more positions on one pool.

If nothing upstream holds a single authoritative number, you oversell, and on marketplace that lands as a cancellation rate against your seller scorecard. AIMS360 keeps one available to sell pool across your DC, your 3PL and your retail stores, then publishes derived positions to each channel, so what Bloomingdale's shows is what you can actually ship. That is our reading of how the architecture behaves rather than something Bloomingdale's states.

The designer floor

Why Bloomingdale's is a vendor brand business

Bloomingdale's carries very little private label relative to Macy's. Its designer jewelry directory lists David Yurman, Marco Bicego, Roberto Coin, LAGOS, Messika, Repossi, Sydney Evan, Longines and TAG Heuer alongside its own Bloomingdale's Fine Collection. Its designer handbag directory lists Bottega Veneta, Chloe, Coach, FERRAGAMO, Longchamp, MARC JACOBS, MZ WALLACE, Polo Ralph Lauren, Tory Burch and TOTEME.

Assortment rotates, and some of those brands trade through concession or licensing rather than wholesale purchase orders, so read that as evidence the floor buys outside brands in these categories rather than proof that any named brand exchanges EDI purchase orders with Bloomingdale's.

What a luxury floor changes operationally

Low unit counts, high unit value Ticketing and packaging are part of the product A single lost carton is a material write off Returns handling is scrutinized Style, metal, stone and size variants on one master

The requirements are the same as Macy's, but the tolerance for error is not. A mis-ticketed unit on a mass floor is an expense offset. On a designer floor it is a unit that cannot be sold at all until it is fixed, and the fix happens in your warehouse, not theirs. That is the case for having the ticket, the carton label, the ASN and the invoice come off the same record in the same system rather than from four tools that reconcile after the fact.

Requirements at a glance

What AIMS360 handles on every Bloomingdale's order

These come from the shared Macy's, Inc. Vendor Standards. The Macy's page carries the full detail on each one.

Required documents 850 purchase order, 856 ASN, 810 invoice and the 832 UPC catalog through OpenText, required from all vendors. 846 from select vendors, plus 820, 852, 855, 180 and 997.
No 860 or 824 Neither appears in any Macy's, Inc. mapping guide index at any version. Purchase order changes arrive as a retransmitted 850, so build for that.
ASN timing Sent immediately after the truck door closes, allowing three hours of processing, so it lands at least 3 hours before delivery. Two structures published, pick and pack and standard carton pack.
Carton labels GS1-128 with SSCC-18 on every carton, 4 by 6 or 3 by 8 inch format, subset C symbology at 20 mil. SSCC numbers never reused.
Item setup A GS1 certificate and company prefix must exist before vendor setup. Codes at the ID, PID, vendor style, color and size level.
Floor ready Pre-ticketed with one UPC per ticket and one EPC per RFID tag, on the correct industry standard hanger. Physical ticket samples approved before first shipment.
Connection OpenText is the preferred VAN for bulk. On dropship you may be required to connect through Rithum and CommerceHub OrderStream instead. Marketplace connects separately through Mirakl Connect.
Non-compliance Expense offsets and invoice chargebacks, deducted from amounts otherwise payable. The schedule is in Appendix H of the Vendor Standards, behind a MacysNet login.

Requirements are issued to each vendor through MacysNet and can change. Confirm your own document set, department scope and RFID requirements after you register rather than relying on any summary, including this one.

Bloomingdale's EDI FAQ

What brands ask before going live

The questions designer, jewelry, handbag and apparel brands raise before starting Bloomingdale's onboarding on AIMS360.

Not for bulk or dropship. The Macy's, Inc. Vendor Standards state that the term Macy's refers to all entities affiliated with Macy's, Inc., including those that operate Bloomingdale's, bloomingdales.com and the Bloomingdale's Outlet Stores. Same portal at MacysNet, same standards document, same UPC catalog provider through OpenText, same Vendor Direct Fulfillment program. Macy's Backstage is the carve out with its own standards, not Bloomingdale's. Where Bloomingdale's genuinely differs is the marketplace and the vendor entity setup.

It is a separate Mirakl storefront, not a shared one, so being live on Macy's Marketplace does not put you on Bloomingdale's. It has its own onboarding and commission structure, settles weekly rather than twice monthly, and Bloomingdale's supplies return labels which are then charged back to the merchant's carrier account. Mirakl also describes Bloomingdale's running three distinct models inside the marketplace: e-concession, complementary assortment and emerging brand incubation. Plan them as two separate integrations.

A model within the Bloomingdale's marketplace rather than a separate integration path. It is aimed at luxury brands that want to control their own assortment and presentation on the Bloomingdale's storefront instead of handing selection to a buyer, which is closer to how those brands operate their own channels. Operationally it is still a Mirakl connection, so it publishes from the same catalog and the same inventory feed as anything else you list there, and it competes for the same physical units as your wholesale and dropship commitments.

Yes. Macy's onboarding documentation names Bloomingdale's and Bloomingdale's Outlet Stores as distinct vendor entities with their own contacts, even though both follow the same Vendor Standards. The shared 856 test and audit request form has a division picklist covering Macy's, Bloomingdale's, Bloomingdale's Outlet Store and Macy's Backstage, which is a good indicator of how the divisions are actually separated on Macy's side. Treat the Outlet as its own account rather than a channel of the main banner.

The same set as Macy's. Required from all vendors: the 850 purchase order, the 856 advance ship notice, the 810 invoice, and the 832 UPC catalog delivered through OpenText. The 846 inventory advice is required from select vendors and is central to dropship. The 820 remittance advice, 852 product activity, 855 acknowledgment, 180 return authorization and 997 functional acknowledgment all have published mapping guides, and there are Vendor Direct variants of the 810, 846, 850 and 856 for dropship. There is no 860 purchase order change and no 824 application advice at any version.

OrderStream. The Vendor Direct Fulfillment standards, which cover Macy's and Bloomingdale's together, name Rithum and CommerceHub and the OrderStream system, and state that in lieu of an EDI connection vendors may be required to use that connection for VDF documents. Dsco is a different Rithum platform, acquired as part of CommerceHub in November 2020, and its verified Macy's, Inc. touchpoint is the marketplace side rather than dropship. Brands often say Dsco when they mean Rithum, usually because they already use Dsco for Nordstrom, Neiman Marcus or Saks Off Fifth. Confirm which platform your Bloomingdale's contact means before you build.

Yes, and the GS1 certificate and company prefix must exist before you can be set up as a vendor at all. Every item then needs a code at the ID, PID, vendor style, color and size level in a GS1 US compliant UPC, GTIN and EAN catalog delivered through OpenText, including collateral, gift with purchase and purchase with purchase items. New catalogs are approved and verified before the data goes live. For jewelry this is where metal, stone and size variants have to resolve cleanly onto one style master, which is exactly the modeling problem a generic ERP handles badly.

A GS1-128 label with a unique SSCC-18 on every carton shipped to a distribution center or direct to store, in either the 4 by 6 inch or 3 by 8 inch format, with subset C symbology at a 20 mil nominal X dimension, and SSCC numbers that are never reused. Merchandise must arrive floor ready, meaning pre-ticketed with exactly one UPC per ticket and one EPC per RFID tag, on the correct industry standard hanger. Physical ticket samples are mailed for approval before the first shipment. Dropship shipments skip this entirely and carry a Bloomingdale's branded packing list instead.

Macy's, Inc. requires tags in accordance with its EPC-Enabled RFID Technical Specifications and states that RFID has rolled out into most families of business. The department scope is published only inside that specification, which requires a MacysNet login, so confirm whether your departments are in scope after you register. Two rules published openly: use integrated UPC and EPC tickets so the physical ticket appearance does not change apart from the EPC symbol, and never transmit EPC numbers in place of UPC, GTIN or EAN codes. Treat any RFID category list you find elsewhere with caution.

Differently from Macy's, which is one of the clearest practical differences between the two storefronts. Bloomingdale's provides the return label and then charges it back to the merchant's carrier account, and returns go to the seller rather than into a Bloomingdale's store. On Vendor Direct Fulfillment the vendor accepts consumer returns directly unless otherwise negotiated. On bulk wholesale, returns to vendor run on the 180 return authorization paired with a reverse 856. Three programs, three return paths, which is worth modeling before you launch the second one.

Yes, and it needs to. Bulk, dropship, Macy's Marketplace and Bloomingdale's Marketplace each publish availability on their own cadence and none of them reserve stock for the others, so the same physical unit can sit in several positions at once. AIMS360 holds one available to sell pool across your DC, your 3PL and your retail stores, and publishes derived positions to each channel. On a designer floor where unit counts are low and unit values are high, that difference shows up as cancellation rate rather than as a rounding error.

Macy's, Inc. routes new merchandise vendor applications through RangeMe and points existing vendors to MacysNet for technical requirements and specifications. EDI onboarding starts after a buyer relationship and an account number exist, and MacysNet registration itself requires a twelve digit account number. Marketplace is the exception: it has its own seller application through Mirakl Connect and does not depend on a wholesale vendor relationship, which is why some brands reach the Bloomingdale's customer through marketplace first and wholesale later.

Why AIMS360

Built for the brands on a Bloomingdale's floor

AIMS360 has spent four decades building software for apparel, footwear, jewelry, beauty and accessories brands. EDI, OMS, WMS, PLM and accounting sit in one platform, so the ticket, the carton label, the ASN and the invoice all come off the same record, and wholesale, dropship and both marketplaces draw on one inventory number instead of four. Read how brands scaled on AIMS360 or book a Bloomingdale's EDI demo.

Related integrations

Department store and luxury EDI

Run Bloomingdale's alongside the rest of your wholesale accounts, from one AIMS360 instance and one inventory pool.

Last reviewed 7 August 2026 by the AIMS360 EDI team. Reviewed against the Macy's, Inc. Vendor Standards, the Macy's and Bloomingdale's Vendor Direct Standards dated April 2026, the MacysNet EDI mapping guide indexes, and Mirakl's published Bloomingdale's marketplace documentation. Requirements are issued to each vendor through MacysNet and can change. The routing guide, the RFID technical specification and the Appendix H schedule of expense offsets are behind a MacysNet login and are not quoted here.

Ready when you are

See AIMS360 run your Bloomingdale's orders

A 30 minute live demo on your own wholesale, dropship and marketplace orders, built for consumer brands.