
Selling Bridal and Fashion Collections to Retailers: How Magento and SAP Business One Handle Sizes, Seasons and Stockist Orders
Many bridal boutiques still order their next collection the slow way: a PDF order form, a few emails back and forth, and a sales rep who confirms availability a day later. The buyer wants one style in six sizes and two colours, and she needs to know which sizes she can have now and which only arrive in March. The process works. It just costs both sides time that neither of them has.
That's the everyday reality for brands like Bianco Evento, an international bridal label that sells its collections through retailers and stockists. Each style comes with its own size range. Some pieces are ready to ship, others only arrive later in the season. And the people ordering are busy shop owners, not procurement departments with time to spare.
The market isn't making it easier. In The State of Fashion 2026, McKinsey and The Business of Fashion expect fashion sales in Europe to grow by only 1–2%. According to FashionUnited's summary of the report, 46% of fashion executives think conditions will get worse this year. With so little growth, every wholesale order counts, and ordering has to be as easy as possible for the retailer.
This post looks at what that means in practice for brands running Magento and SAP Business One, using Bianco Evento as the example.
Key takeaways
- Fashion wholesale is harder than most B2B: one style quickly becomes dozens of size, colour and length variants, ordered by look rather than item number.
- A size grid lets boutiques order a whole size run on one screen – show every size, grey out the unavailable ones and keep size ranges per style.
- Replace “out of stock” with real “ships from” dates from SAP Business One, keep pre-orders separate and show approved stockists their own price lists.
- A native B2B app, like the one Ingold built for Bianco Evento, lets retailers reorder from their phone or tablet at fairs, in the showroom or on the move.
Why fashion wholesale is harder than most B2B
A screw manufacturer sells a part. A bridal brand sells a style, and one style quickly turns into a product line: six sizes in two colours is already twelve variants, and a choice of length takes it to twenty-four, all for a single dress.
Buyers work the same way. A boutique doesn't ask for item 4711; it orders a few looks from the new collection, in the sizes its brides usually need. Orders also come in different shapes: a sample for the showroom, stock for the rail, and sometimes one dress for a bride who has already said yes. Each of them can carry its own prices, delivery times and terms.
A standard online shop isn't built for any of that, so fashion needs a B2B setup designed around it.
What retail buyers now expect
For a long time, fashion wholesale ran on trade fairs, sales reps, PDF order forms and a lot of email. That still works. It just isn't enough any more.
McKinsey's 2026 B2B Pulse survey asked around 4,000 business buyers how they purchase. They use about ten different channels along the way. 73% would place an order worth more than $50,000 online. And at B2B companies that already sell online, around a third of revenue now comes in through digital channels.
Boutique owners are no different. They still love the trade fair and the personal call. But when they want to reorder a bestseller at 10 p.m., they want to do it there and then, not wait for office hours.
Order a whole size run on one screen
According to Magento, if a dress comes in a wide range of colours and sizes, it is set up as a configurable product.
That's fine for a bride shopping for herself. For a boutique ordering eight dresses in five sizes, picking one size and adding it to the cart, then starting over for the next, gets tedious fast. A size grid takes that repetition out of the order: one row per colour, one column per size, and a quantity box at each intersection. The buyer fills in the numbers and adds the whole grid to the cart in one go. Magento has no grid of that kind out of the box, so you add one with an extension or a small custom module. Two details make a big difference:
- Show every size, even the ones that can't be ordered. Grey them out instead of hiding them. A buyer who doesn't see size 28 assumes it doesn't exist. A buyer who sees it greyed out knows to ask.
- Keep size ranges per style. Not every dress is made in every size. Bianco Evento, for example, publishes the available sizes style by style, so stockists can see straight away which range a particular gown comes in.
Seasons, pre-orders and delivery dates
Fashion sells ahead of time. Retailers order next season's collection months before it's ready, so the shop has to handle things that can be ordered but aren't in stock yet.
The simple fix is to stop showing a plain "in stock" or "out of stock". Show a date instead: "available now" or "ships from 15 March". That date shouldn't be a guess typed in by hand. It should come from the open production or purchase orders in SAP Business One, so it changes automatically when production moves.
Keep pre-orders and stock orders apart behind the scenes, too. They're often invoiced and shipped at different times, and a boutique doesn't want one waiting for the other.
Stockist accounts and prices
Wholesale prices are for approved retailers only. In practice, that means:
- new retailers register and are approved by hand before they see prices
- each stockist gets the price list that matches their agreement in SAP
- minimum order quantities apply where needed, for example per style or per order
- sample orders can run on different terms from stock orders
The prices themselves should come straight from SAP Business One. How that works, and where it usually goes wrong, is covered in our post on syncing SAP price lists to Magento.
Case study: Bianco Evento's B2B app
Bianco Evento's buyers are rarely sitting at a desk. They're in their boutique, at a bridal fair, or travelling between appointments. So alongside the online presence, Ingold Solutions built Bianco Evento a native B2B app for iOS and Android.
The idea is simple. A retail partner opens the app on her phone or tablet, looks through the collection, and places her order there, without logging into a laptop or waiting for a sales rep to call back.
Why an app and not just a mobile website? A few practical reasons:
- Reordering is quicker. The buyer is already logged in, and her last orders are one tap away.
- It works where the buying happens. At a trade fair or in the showroom, a tablet is far easier to hand around than a laptop.
- Brands can reach buyers directly. A push message when a new collection lands gets noticed faster than another newsletter.
Ingold builds B2B and B2C apps like this for brands on Magento, and also for shops running on Shopify, Shopware and WooCommerce.
Where SAP Business One fits in
The shop and the app are what the retailer sees. SAP Business One is what keeps them honest. The split looks like this:
| SAP Business One looks after | The shop and app look after |
|---|---|
| Stock per warehouse | Showing availability in plain words |
| Production and purchase orders | Turning those into "ships from" dates |
| Stockist price lists and terms | Showing each retailer her own prices |
| Orders, invoices and payments | Taking the order quickly and confirming it |
The two are joined by a connector that moves stock, prices, customers and orders between them. Ingold's SAP Business One Magento connector does exactly this job, so a retailer's order lands in SAP without anyone typing it in again.
A short checklist before you take wholesale online
If you sell a fashion or bridal collection through retailers, check these before you build anything:
- Are the size ranges per style correct in your system, or only in a PDF?
- Do you have a clear approval process for new stockists?
- Can you get a real "ships from" date out of your production planning?
- Are sample orders and stock orders handled separately?
- Do your best buyers want to order on a phone or tablet?
If you answered "not really" to two or more, start there. The shop or app is the easy part once this groundwork is done.
Frequently asked questions
+Can Magento handle B2B fashion orders with many sizes and colours?
Yes. Each style is set up as a configurable product with one variant per size and colour. For wholesale buyers, a size grid lets them order a full size run on one screen. That grid is usually added with an extension or a small custom module.
+How can retailers pre-order a collection that isn't produced yet?
Show a "ships from" date instead of "out of stock" and let them order anyway. The date should come from the production or purchase orders in your ERP, so it updates on its own when plans change.
+Does a fashion brand need a B2B app as well as a web shop?
Not always. An app makes sense when your buyers order on the move, at trade fairs or between appointments, and reorder often. Bianco Evento, for example, went with a native app for iOS and Android.
+Can stockists see different prices from end customers?
Yes. Approved retailers log in and see the price list from their agreement in SAP Business One. Everyone else sees retail prices, or no prices at all.
+How does SAP Business One connect to a Magento fashion shop?
Through a connector that moves products, stock, prices, customers and orders between the two systems, so orders reach SAP without being typed in again.
Selling your collection to retailers?
Ingold Solutions builds B2B shops and apps for fashion and bridal brands, connected to SAP Business One. We're an Adobe Solution Partner, Hyvä Partner and SAP Silver Partner, and Bianco Evento's retail partners already order through an app we built. Let's look at how your retailers order today, and what would make it easier for them.



