Intelligent routing: Rule sets

Rule sets tab (Inventory › Intelligent routing › Rule sets) is where you tell the system "which products, how boldly should I act." A rule set defines three things:

• Which products: all products, a product group, or a single product.
• How much protection: how confident you are that a product will run out on our own site before reducing the quantity shown on the marketplace (protection level) and safety limits to prevent excess.
• How it operates: whether it only monitors, waits for your approval, or applies itself (operation mode).

A rule set does not affect stock, reservation, or safety stock rules; it only sets or removes an upper limit on the quantity shown on the marketplace.

List

The list shows each rule set's name, which products it applies to, protection level, operation mode, status, last publication, and number of tracked products. Clicking a row's name opens details.

Operation mode is shown only on the published set; draft shows "Not yet published." Use the filter above the list to view active (draft + published), draft, published, or archived sets. The number of tracked products updates after publication scanning.

Scope and priority

If multiple rule sets apply to a product, the more specific scope takes precedence:

single product › product group › all products

Only one rule set per scope (e.g., "Product group: AYK") can be published simultaneously. Attempting to publish a second set for the same scope triggers a warning "Another rule set is published for these products: …" with a link to that set; you must archive it first or choose a different scope.

Rule sets cannot currently be created by brand or category (these data are not in inventory). Use product group or single product.

Inheritance

Any setting left blank in a narrower scope set inherits from the upper rule set: in a single product set, first from the product's group published set, then from the all products set. If none above, system defaults apply. Manually entered values (including 0) always take precedence.

The wizard shows under each field what value will be inherited if left blank, e.g., "If left blank, from upper rule: 95% (All store · All products · Cautious)." The Active settings table on the detail page also shows the source of each value.

Protection levels

Percentages reflect current system settings; cards on screen always show current values. Level also determines how many days ahead stock depletion is checked and how much more profitable our site must be compared to the marketplace. Days only define the horizon: system checks if stock will run out within N days at current sales speed; increasing days raises depletion probability. You can adjust these individually in Detailed settings.

Exit threshold: a protected product will not exit protection until its depletion probability falls 5 points below the entry threshold (e.g., enters at 85% for Balanced, exits below 80%). This prevents products near the threshold from toggling hourly. If sales on our site fall below expectations, the product reopens on the marketplace regardless of this threshold.

Safety limits

Setting zero may cause the product to appear "sold out" on marketplace; the wizard warns about this. Allowed ranges are shown under each field.

When does reopening occur? The system monitors sales of a protected product on our site for at least 4 hours and expects sufficient sales during this period. If actual sales fall below the selected percentage of expected sales and the system confirms this is not random, it gradually reopens the product on the marketplace. This check runs only after limits have actually been applied to the marketplace; counters do not start for reductions waiting your approval. In "Monitor, do not apply" mode, monitoring starts when the recommendation is made.

Profit thresholds

"How much more profitable must our site be" and "Minimum extra profit for intervention" settings carry profitability data. Users without View profitability or Edit profitability permissions see these fields as "Hidden" and cannot change them; saving a draft preserves existing values.

Wizard

<video controls preload="metadata" playsinline poster="https://files.docs.hebiar.com/videos/console/inventory/routing/kural-seti-ve-dene.en.jpg" src="https://files.docs.hebiar.com/videos/console/inventory/routing/kural-seti-ve-dene.en.mp4"><a href="https://files.docs.hebiar.com/videos/console/inventory/routing/kural-seti-ve-dene.en.mp4">Open video</a></video>

Create rule set (or Edit in details) opens a 4-step wizard:

1. Which products? Name and select scope. After selection, live counts appear, e.g., "This selection includes 182 products; 64 sell fast on our site and have stock on marketplace." The system only considers fast-selling products with marketplace stock; others remain unchanged on marketplace. You can proceed if count is unavailable.
2. How much protection? Choose protection level. The "Your selection means" box summarizes the choice.
3. Safety limits. You can continue with recommended values. The "Example" box shows minimum marketplace quantity for a product with 100 units.
4. Test and publish. Review summary and choose next step: Save as draft, Save and test, or (if authorized) Save and publish.

Each Next auto-saves the draft; you can close and resume later from the list. Exiting with unsaved changes prompts options: "Save and exit," "Exit without saving," or "Stay in wizard." Errors return you to the step with instructions.

Editing a published set saves changes as a draft; the published version remains active until you publish.

Test: how to interpret results?

Test evaluates the rule set once with today's sales and stock data, answering "What if this rule were active now?" It does not write to any channel. It does not replay past days, so time-dependent numbers like "would have reopened later" are not shown. Testing runs in background; results appear here when done; you can leave the page while waiting. Results also appear on detail page and Operations tab. Only one test can run at a time.

Results include:

• Would reduce on our channel: number of products for which marketplace quantity would be reduced.
• Would remain balanced: evaluated, no intervention needed.
• Could not evaluate: products lacking data; reasons and counts shown (e.g., "Marketplace profitability data missing: 2 products," "Purchase rate missing").
• Estimated extra profit: estimated benefit of protection; not guaranteed. Users without profitability view permission see "Hidden."
• Example products: up to 10 products; for each, marketplace quantity and a simple rationale, e.g., "We sell an average of 9 units daily on our site; with 60 units in stock, it will likely (97%) run out in 7 days. Our site earns 180 ₺ per product, Trendyol marketplace earns 120 ₺; therefore, maximum 6 units are shown on Trendyol." Users without profitability view see "more profitable" instead of amounts. If no sales on our channel in last 28 days, a faint note appears: "Product price used for calculation; same price assumed for marketplace; profit difference comes only from commission and expenses." This note appears even without profitability permission (without amounts). For unevaluated examples, only the first sentence appears as profit is not calculated.

If most products cannot be evaluated due to missing profitability data, the screen directs you to the Channel profitability tab. If you change the rule set after testing, results show "changed after this test" warning; retest is recommended.

Publishing and operation modes

<video controls preload="metadata" playsinline poster="https://files.docs.hebiar.com/videos/console/inventory/routing/yayinlama.en.jpg" src="https://files.docs.hebiar.com/videos/console/inventory/routing/yayinlama.en.mp4"><a href="https://files.docs.hebiar.com/videos/console/inventory/routing/yayinlama.en.mp4">Open video</a></video>

In the Publish window, select operation mode; each option explains its effect:

Selecting automatic apply shows an additional confirmation checkbox. The system has a safety brake: if many new restrictions occur in a short time, automatic application pauses and new restrictions await your approval; reopenings always proceed.

Publishing an untested (or changed after test) set warns you and suggests "Test first."

After publishing, detail page shows status:

• Published and Intelligent routing enabled: system activated; scoped products scanned in background.
• Published but Intelligent routing not enabled: rule set saved; try enabling again from Summary tab.
• Published; not running due to emergency stop: emergency stop prevents auto-start; start manually with Restart on Summary tab.
• Scan start status and warnings also appear here. If sales data is outdated, message "Waiting for sales data; products will scan automatically when data arrives" appears; this is not an error.

Change operation mode changes only the mode without affecting published settings (creates new version). Switching to "Monitor, no apply" removes applied limits on marketplace in next decision cycle.

Versions and rollback

Each publication is a new version. Version history shows who, when, and with which operation mode published; Show content opens manually entered settings for that version.

Rollback publishes the selected older version's settings and scope as a new version. A reason is required (minimum 5 characters). The rule set's name and operation mode do not revert: for security, a set switched to "Apply with my approval" or "Apply automatically" will revert to "Monitor, no apply" when rolled back. Unpublished draft changes are discarded on rollback.

Archiving, restoring, and deleting

Archive stops a published set. Products in archived sets lose protection on next scan and appear normally on marketplace. Archived sets cannot be edited, tested, or have operation mode changed.

Restore from archive reactivates an archived set. Use the button on detail page or Restore with this version in version history to select which version to restore; the last version before archiving is selectable. The selected version's settings and scope publish as a new version; the rule set name remains current. A reason is required (minimum 5 characters).

For security, operation mode is checked:

• If the set was "Apply with my approval" or "Apply automatically" before archiving, it reopens as "Monitor, no apply": decisions are saved but marketplace is unchanged. The window warns this; after restoring, a notification says "Opened as Monitor, you can change operation mode anytime." Use Change operation mode to switch to applying.
• If already "Monitor, no apply," it reopens as is.

Restore from archive is blocked if:

• Another rule set is published for the same products: archive that first (window links to it).
• The rule set name is currently used by another set (published or draft): rename or archive that set first.
• The rule set was archived without ever being published: create a new rule set with the same settings.

Restoring does not automatically enable Intelligent routing; if system is off, enable it from Summary tab.

Unpublished drafts can be deleted with Delete draft; this does not affect marketplace.

Permissions

Buttons for unauthorized actions are visible but disabled; the required permission is shown below.

Frequently asked questions

Does publishing a rule set immediately change anything on the marketplace? No with "Monitor, no apply." With "Apply with my approval," only approved decisions apply. With "Apply automatically," changes start from the next decision cycle.

Why does product group set recommend "Inherit from upper rule" for level? So settings in the all products set apply to narrower scopes. Choose Cautious / Balanced / Bold if you want different behavior; this overrides the inherited value.

Why does test say "Could not evaluate"? Usually missing profitability data, purchase rate, or sales data. The reasons list shows what is missing and how many products are affected.

What if the system stops? Applied limits automatically lift within 45 minutes; no sales are lost due to malfunction. Use Emergency stop at top of page to remove all limits immediately.

Can I restore an archived set? Yes. Press Restore from archive on the archived set detail and select a version. If the set was "Apply with my approval" or "Apply automatically," it reopens as "Monitor, no apply" for safety; switch operation mode later to apply.

More Q&A: Frequently asked questions.

Related articles

• How it works — three decisions, operation modes, safety measures, and durations
• Channel profitability — missing data if test says "Could not evaluate"
• Decisions — monitoring and approving decisions after publishing
• Operations — testing and finding products to track
• Summary — reopen and emergency stop
• Intelligent routing — getting started and initial setup sequence