Setting up Minimum Order Quantity in 1C-Bitrix

In a wholesale online store, each item is sold only in batches — of 6, 10, or 100 units. If a customer adds 5 instead of 6 to the cart, the cart either rounds the quantity up to the minimum or throws an error. At first glance, this is a simple setting via the admin panel. But in practice, when the catalog has 10,000 items and the batch depends on the supplier's packaging, manual editing becomes a nightmare. One of our clients with a catalog of 12,000 items spent a week setting values manually and still made errors in 15% of cases. We automated the process via CSV import and a synchronization script with 1C, reducing time to two hours.

In Bitrix, the minimum batch is set by the MIN_QUANTITY field in the b_catalog_product table. Additionally, STEP_QUANTITY is used — the quantity step (multiplicity). When a product is added to the cart, the catalog module reads MIN_QUANTITY and automatically raises the quantity if the customer entered less. Important: the field does not affect discounted prices and does not depend on stock — only the product itself.

Where it is stored and how MIN_QUANTITY works

Each product has a record in b_catalog_product with the following fields:

• MIN_QUANTITY — minimum order quantity (decimal, default 1)
• STEP_QUANTITY — quantity increase step (multiplicity, default 1)

If MIN_QUANTITY = 0 or 1, the restriction does not apply. When adding to the cart, the system reads MIN_QUANTITY and, if the entered quantity is less, automatically raises it to the minimum (depends on the cart component setting).

Setup via the administrative interface

Catalog → [select product] → SKU/Quantity

Field "Minimum order quantity" — enter a number. Value 0 or 1 means no restriction. For mass assignment, use import via CSV or XML (Catalog → Import), where in the column MIN_QUANTITY you specify the desired value.

How to set the minimum batch for 10,000 products?

If there are many products, manually editing each one takes a week. The optimal way: import via CSV with file generation in Excel or on the 1C side. The column MIN_QUANTITY is present in the catalog export. For wholesale items, you can set a value of 6, for retail — 1. After importing, be sure to check consistency with STEP_QUANTITY (an error here is a common cause of cart malfunction). CSV import is 50 times faster than manual editing for 10,000 products.

Setup via API: step-by-step instructions

1. Get the product or SKU ID (e.g., via CIBlockElement::GetList).
2. Call \Bitrix\Catalog\Model\Product::update($elementId, ['MIN_QUANTITY' => 10]).
3. Ensure the catalog cache is cleared (use the ClearByTag method).
4. Verify in the cart that the new value is applied.
5. For mass assignment, run a loop in an agent or script.

\Bitrix\Catalog\Model\Product::update($elementId, [
    'MIN_QUANTITY' => 10,
]);

This method is preferable to CIBlockElement::SetPropertyValues because it works directly with the b_catalog_product table and triggers caching. We use it in custom agents for ERP synchronization.

Why doesn't MIN_QUANTITY work in headless frontend?

The standard component bitrix:sale.basket.basket reads MIN_QUANTITY and automatically adjusts the quantity. But if the frontend is headless (React, Vue), then MIN_QUANTITY must be fetched via REST API (catalog.product.get method) and client-side validation implemented. Otherwise, the customer may send 5, and the server will accept the order without validation — a cart error.

How to synchronize MIN_QUANTITY and STEP_QUANTITY?

If both a minimum batch and a step (STEP_QUANTITY) are set, the minimum quantity must be a multiple of the step. Example: MIN_QUANTITY = 6, STEP_QUANTITY = 3 — correct (6/3=2). But MIN_QUANTITY = 5, STEP_QUANTITY = 3 — leads to the cart raising the quantity to 6 (the next multiple), but the customer sees an unexpected change. We check this consistency automatically with a script.

Setup methods: comparison

Typical errors and their solutions

Delivery time

Basic setup of the minimum batch for one product or a group via import — from 2 to 4 hours. Includes: analysis of current data, file preparation, import, cart verification, fixing consistency errors. If a script for automatic synchronization with 1C is required, the time increases to 1 day.

What is included in a turnkey setup

• Audit of existing MIN_QUANTITY and STEP_QUANTITY values across the entire catalog
• Preparation and execution of mass import (CSV/XML)
• Writing an API script (if automation is needed)
• Checking cart operation in standard and custom components
• Brief support documentation
• Consultation on headless frontend (if relevant)

We are certified Bitrix specialists with implementation experience in over 50 catalog configuration projects for wholesale and retail trade. We guarantee stable cart operation after changes. Reduced catalog maintenance costs and up to 80% time savings are expected results.

Official 1C-Bitrix documentation — MIN_QUANTITY will help you understand the nuances.

For mass setup or complex scenarios (integration with 1C, custom step, stock check) — contact us. We will evaluate your project within 1 working day and offer the optimal solution. Get in touch for a catalog audit. Apply for a detailed analysis — receive a consultation.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.