Dealer Sales Software in Textile Wholesale: Season, SKU and Payment Term Order

A single model produces dozens of SKUs through size and color combinations. Say your 'Aurora' brand basic crew-neck t-shirt comes in 5 colors, white, black, navy, khaki and burgundy, and carries 6 sizes from S to XXL. That makes 30 separate stock items. The moment you try to enter a dealer order into Excel color by color and size by size, errors become inevitable: deductions from the wrong item, missing shipments and the reconciliation gaps that follow. Standard wholesale programs either don't recognize this matrix at all or force you into one-by-one item entry.

In B2BPro, each model is defined as a parent product, and the size-color combinations underneath it are kept as separate SKUs. The Product and Pricing module and the Warehouse module manage this variant matrix together under the parent product. You enter the dealer order on a single screen as a matrix: color in the rows, size in the columns, quantity in the cell. Stock is tracked separately for every variant, and the order deducts from the correct item the moment it is placed.

The assortment case logic comes into play here as well. Most dealers take a ready-made set rather than a single size: for example a standard case containing '2 S, 2 M, 3 L, 2 XL, 1 XXL'. These sets are defined once, the dealer opens an order on a per-case basis with a single click, and the system automatically distributes the case across the variant items. The Order and Sales module builds this flow around the reality in the field, and size-color errors drop almost to zero.

What defines textile is the tempo of the season. A collection is planned, produced, distributed and sold within a few months. That is why price is not single: the start-of-season list price, the end-of-season outlet price and the discount that varies by dealer group can all apply to the same product at the same time. A dress listed at 420 TL in March in the spring-summer collection drops to 189 TL on the outlet channel in August; on top of that, group A dealers get a 12 percent discount and group B 8 percent. Managing these three layers manually is the main source of pricing errors.

The Product and Pricing module holds multiple price lists on a season and collection basis. For the same SKU, it defines the 'Spring-Summer 2026 List', 'End-of-Season Outlet' and dealer group prices as separate lists, and you set which list applies to which dealer. When a representative or dealer opens an order, the correct price comes up automatically.

Clearing end-of-season stock, on the other hand, is the job of the Discount and Campaign module. It defines rules such as '25 percent off when you buy a case of remaining winter coats' or 'a special assortment campaign for certain dealers', and the system applies them automatically on the order. If you want to go deeper into the logic of pricing, the payment term and credit limit article clarifies how commercial terms combine with price.

The most critical moment of a new collection is reading demand before production even begins. You show the fall-winter collection in the showroom in June and collect orders for September delivery; the quantities gathered feed directly into the production plan. A wrong forecast is a loss in both directions: the model you under-produce sells out early, and the one you over-produce clears at the outlet at season's end. Being able to take sound orders for products not yet in stock is essential.

The Order and Sales module supports the pre-order flow. Dealers see the collection in the showroom or through the dealer portal and open an order before the product even enters stock. The system keeps these orders separately as 'pre-orders', and the collected demand forms the basis of the production plan. For example, an 18,000-unit pre-order gathered from 240 dealers clarifies which model will be produced in how many colors.

When the shipment arrives, pre-orders are linked to the relevant items, allocated to the dealer automatically, and the remaining stock is released for open sale. This way you carry out planned production and distribution without missing the season tempo. If you want to see in advance when each dealer will reorder, Demand and Reorder Forecasting, available in early access, is being developed to derive that prediction from order history (not yet live).

In textile, returns and exchanges are not an exception, they are the process itself. Products come back because the size doesn't fit, they don't sell or they are defective; the collection left on hand at season's end returns through the return channel. The problem is not the return itself but tracking it. When a returned product re-entering stock from the correct variant, and the amount reflecting correctly on the dealer's current account balance, is done manually, both stock and balance go wrong and dealer reconciliation collapses.

In B2BPro, the Order and Sales module and the Current Account Management module record the return-exchange flow together. The return item re-enters stock on a variant basis: if the dealer returns 12 units of navy in size L, they are written back to exactly that SKU. The amount reflects on the dealer's current account balance automatically, and in size exchanges the difference calculation is kept in the system.

This automatic reflection keeps end-of-season reconciliation healthy. To understand how the current account works from the ground up, the what is a current account article helps, and to see how return and payment items meet in a single table, the what is reconciliation article helps. Balance and stock errors caused by returns disappear once the recording is automated.

In textile wholesale, the sales relationship runs largely through the showroom, trade fairs and the field representative. The dealer sees the collection on site, and the representative wants to enter the order right there. But if the representative doesn't have current stock, the season price and the dealer's current account balance at hand, the order gets written on paper and entered into the system back at the office in the evening; by then stock may have changed, the price may be off and the dealer's limit may be full.

With the mobile app of the Field Sales module, the representative sees the current collection, variant stock, season price and current account balance instantly in the showroom, at the trade fair or at the dealer. They enter the order on site with the correct price and correct stock. Before an order is opened for a dealer exceeding the credit limit, the system warns, so uncontrolled term-based selling in the field is prevented.

The Dealer Quote module is used to present a collection quote to the dealer: the representative prepares the assortment-based quote, shares it with the dealer, and the approved quote turns into an order with a single click. If you want to see the conversion in the field end to end, the field sales automation article describes the entire process.

In textile, collections are mostly term-based: 30-60 day open accounts, checks and promissory notes are common. You ship the collection and receive the money weeks later; meanwhile production and new collection payments are at the door. When matching the incoming wire/EFT to the correct dealer, tracking the due date day by day, and recording the check are done manually, cash flow becomes invisible and overdues grow.

Current Account Management and the Collections module track the open account, the payment term, checks and notes on a single panel; they define a credit limit for each dealer and halt the order flow when the limit is exceeded. The Bank Integration module automatically offsets the incoming payment against the relevant current account and closes the reconciliation without manual effort. For concrete methods of reducing overdue receivables, this guide is a useful starting point.

For fast collection, with the Payment Gateway and Dealer Payment Link you take 3D Secure credit card collections from the dealer: you send a link and see the payment instantly. The Collections Assistant, which flags in advance which dealer will pay late and prepares a gentle reminder draft, is being developed in early access (not yet live), designed to prevent delays before they grow.