Skip to content

Kentro OS · Automation rules

Ecommerce automation for the decisions your team makes the same way every day

Set a rule once and Kentro OS applies it to each order as it arrives: which warehouse ships it, which carrier it uses, how it is tagged and what shipping costs. Exceptions such as stock at risk and late orders show up as findings in Kentro IQ, with a suggested next step for a person.

  • Routing by warehouse, vendor or zone
  • Carrier and insurance preselection
  • Tags, holds and shipping rates
  • Included in every Kentro OS plan
Rules applied to orders as they arrive

What is ecommerce automation?

Ecommerce automation is software applying the decisions your team makes the same way every time: where an order ships from, which carrier it uses, how it is tagged and what it costs to ship. In Kentro OS, an ecommerce ERP, a rules engine makes those decisions as orders arrive, and Kentro AI lists findings that still need a person.

What it does

Rules for the routine, findings for the exceptions

Route orders as they arrive

A routing rule sends matching orders to a warehouse you choose, to the warehouse for the fulfillment zone of the destination, or to a vendor that drop-ships. Rules run in priority order for each sales channel and the first one that matches decides. With no match, the order goes to the channel default warehouse.

  • Route to a warehouse, to a vendor or by fulfillment zone
  • Priority order, and the first match decides
  • A warehouse pinned by hand on one order overrides the rules
Ecommerce order management
Orders routed to different warehouses by rule

Preselect the carrier and the insurance

Rules can preselect the carrier and service, and whether a shipment is insured, for orders that match. The ship screen opens with those choices already made, and the person shipping can still change them.

  • Carrier and service preselected
  • Insurance by product value, by a fixed amount, or off
  • The operator can override on the ship screen
Shipping and labels
A ship screen with the carrier already selected by a rule

Tag orders and hold them out of the queue

A tagging rule adds or removes tags on matching orders. The same rule can keep an order out of the shipping queue, mark it as a backorder or set third-party carrier billing, so special cases are separated before anyone picks them.

  • Add or remove tags
  • Hold an order out of the shipping queue, or mark a backorder
  • Bill shipping to a carrier account you name
Orders tagged by a rule as they arrive

Set shipping charges, discounts and price lists by rule

Shipping rate rules decide what an order is charged for shipping: free, a fixed price, a percent of the subtotal, the carrier rate or the carrier rate with an adjustment. Discount rules take a dollar amount or a percent off the subtotal, and price list rules apply a price list to matching orders.

  • Free, fixed, percent or carrier-rate shipping
  • Dollar or percent discounts
  • Price lists applied by rule
An order with a shipping charge set by a rule

Findings for what a rule cannot decide

Rules handle the cases you can describe ahead of time. Kentro IQ watches for the rest, such as stock at risk and late orders, and lists each finding with a suggested next step. Mark a finding done when it is handled, or skip it with a reason.

  • Stock at risk and late orders
  • A suggested next step on each finding
  • Mark done or skip, in the app or in chat with Kentro AI
Kentro IQ analytics and findings
A list of findings, each with a suggested next step

Rule types

What the rules engine in Kentro OS can do

Rule types in the Kentro OS rules engine and what each one does
Rule typeWhat it does
Fulfillment routesSends an order to a warehouse, to a vendor or by fulfillment zone. Preselects the carrier, service and insurance.
Order taggingAdds or removes tags, holds an order out of the shipping queue, marks a backorder, sets third-party carrier billing.
Shipping ratesFree shipping, a fixed price, a percent of the subtotal, the carrier rate or an adjusted carrier rate.
Custom discountsA dollar amount or a percent off the subtotal.
Price listsApplies a price list to matching orders.
PO provisioningCreates purchase orders for orders that carry chosen tags, on a schedule, for a chosen warehouse.
Event handlersReacts to an event, such as received inventory, by sending an email from a template or tagging the record.

Each rule has conditions on order facts such as tags, the customer, the order total and the ship-to or bill-to address, a priority, and the sales channels it applies to.

One job, three ways

Review what needs attention this morning, three ways

Review what needs attention this morning

  1. In the app

    Open the fulfillment queue and the findings list. Rules have already routed and tagged the new orders, and the findings show what is left for a person.

    The fulfillment queue with orders already routed and tagged
  2. With Kentro AI

    Ask "What needs my attention today?" Kentro AI lists the open findings with their next steps, and marks one done when you tell it to.

    Kentro AIIn Kentro
    1. you ›What needs my attention today?
    2. getRecommendationsRead the open findings for the workspace
    3. getFulfillmentPipelineRead open fulfillment orders by status and age
    4. Three findings are open: two SKUs at risk of running out and one group of late orders. Each has a suggested next step. Mark any of them done?

  3. With your agent

    Your agent starts from the daily-ops-digest prompt over MCP, reads findings with getRecommendations and the queue with getFulfillmentPipeline, and can mark a finding done with actOnFinding. It cannot create or change rules: a person with the admin permission does that in the app.

    ClaudeConnected to Kentro over MCP
    1. you ›Give me the morning digest and close what I already handled.
    2. getRecommendationsRead the open findings over MCP
    3. actOnFindingMarked one finding done, with the reason you gave
    4. One finding is closed. Two are still open, with the next step for each.

Questions about automation in Kentro OS

What can I automate in Kentro OS?

Decisions on orders, mostly. Rules route an order to a warehouse, to a vendor or by fulfillment zone; preselect the carrier, service and insurance; add or remove tags; hold an order out of the shipping queue or mark it a backorder; set the shipping charge; apply a discount or a price list; and create purchase orders for tagged orders on a schedule. Kentro does not claim to automate everything. Kentro IQ findings cover exceptions such as stock at risk and late orders.

How do rules decide which one applies to an order?

Each rule has a type, conditions, an action, a priority and the sales channels it applies to. For routing, Kentro checks the rules for the channel of the order in priority order, and the first rule that applies decides where the order goes. A rule can also be reversed, so it applies when its conditions do not hold. If no rule applies, the order goes to the default warehouse of the channel.

Is there a visual workflow builder?

No. Rules are forms: you pick the rule type, add conditions on order facts such as tags, the customer, the order total or the address, choose the action and set the priority. There is no drag-and-drop canvas. Creating and editing rules needs the admin permission, so a routing change is always made by someone who is allowed to make it.

Can AI agents create or change automation rules?

No. Rules are created and edited in the app by a user with the admin permission. Kentro AI and agents connected over MCP read orders, the fulfillment pipeline and findings, and they can mark a finding done or skipped with a reason. They do not route orders, change rules or buy labels.

What are Kentro AI findings, and how are they different from rules?

A rule acts on an order by itself, the same way every time. A finding is something Kentro IQ noticed that a person should decide, such as a SKU about to run out or an order that is late, listed with a suggested next step. You handle it and mark it done, or skip it with a reason. Rules remove routine decisions; findings make sure the exceptions are seen.

Let rules handle the routine orders

Start with one routing rule and one tagging rule, then add the next case as it comes up.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy