Programmable RFQ and order intake
Turn messy requests into quote-ready orders.
OrderRail transforms emails, chats, PDFs and spreadsheets into traceable RFQs, applies your merchant rules, and prepares quotes or draft orders for review.
Start with one product line. Keep the channels your customers already use.
RFQ-0248
Keep the way your customers already send requests
01Commerce does not start in a cart
Your customers know how to send a request. The hard part begins after it arrives.
Email, files and notes are only the start. Your team still has to find data, clarify details, calculate a price and recreate the transaction.
OrderRail turns this manual chain into one controlled workflow.
02One flow from request to transaction
Keep the workflow simple. Make every decision clear.
Information moves onto a rail with an explicit source, rule and control point.
- 01 / RECEIVEIN
Receive the request anywhere
Email, chat, uploads and APIs enter through the same gateway.
Received - 02 / STRUCTURE{ }
Extract fields with evidence
Each value links to a message, file, prior order or tool that produced it.
Sourced - 03 / APPLYJS
Apply your business logic
Schema, catalog, pricing formulas, capacity and approval policies.
Checking - 04 / EXECUTEGO
Review, then create the transaction
Send the RFQ, quote or draft order to Medusa or another connected system.
Awaiting review
03An inspectable example
See what OrderRail understands.
Choose a request to inspect extracted fields, evidence, tool results and the suggested next action.
“Repeat 5,000 boxes from PO-1032, switch from matte to gloss lamination, and deliver before month end.”
04Merchant-specific logic
The workflow is shared. The business logic is yours.
Every merchant keeps its own schema, rules, formulas and approval policies on the same runtime.
No OrderRail core fork required.Merchant A
Calculates the price automatically once all fields are confirmed.
AUTO-CALCULATEMerchant B
Checks machine capacity before committing to a delivery date.
CAPACITY-FIRSTMerchant C
Prepares a structured RFQ for an operator to price manually.
MANUAL-PRICE05Evidence and control
AI proposes. Your systems and policies decide.
OrderRail lets your team review exceptions instead of recreating entire transactions.
- 01Every important field has a source.
- 02Confirmed values are not silently overwritten.
- 03Financial actions require explicit policy.
- 04Operators review exceptions, not entire transactions.
“Switch from matte to gloss lamination, deliver before month end.”
- 1Source message
- 2Evidence
- 3Structured field
- 4Operator approval
- 5Created order
06Printing and packaging
Start with the product line that creates the most quoting work.
OrderRail does not assume every industry works the same way. The first pilot focuses on one product family and the fields that actually determine the quote.
Repeat order
Faster pathStart from a confirmed specification and review only what changed.
New RFQ
ClarificationTurn a partial request into fields, questions and calculation results.
07From intent to execution
Intake is only useful when it reaches execution.
- INExisting channel
- GWOrderRail Gateway
- JSRules & tools
- OKReview
- MEDMedusa
- FULPayment & fulfillment
Medusa is the first commerce execution adapter. OrderRail stays focused on business-intent workflows and can connect to other systems.
08Operator experience
Give your team a review queue, not another inbox.
Open source evidence, correct one field, rerun a tool, send a clarification or approve the transaction with the full context in view.
5,000 cosmetic boxes · PO-1032
09Design-partner pilot
Configure one real product line. Process live requests.
Start small, evaluate historical data, then process live requests once the workflow meets your team's standard.
Apply for a design-partner pilot Implementation-assisted · Paid setup · Subscription after launch- One product family
- One merchant workflow
- Historical sample evaluation
- One calculation or lookup tool
- RFQ review experience
- Medusa draft-order conversion
10Frequently asked questions
Set the scope before you start.
OrderRail is a normalization and business-intent orchestration layer, not another chatbot or ERP.
Is OrderRail a chatbot?
No. Chat can be an input channel, but the product is RFQ state, validation, rules, tools, approvals and commerce execution.
Does OrderRail replace our ERP?
No. OrderRail standardizes the request before sending trusted data into Medusa, your ERP or another existing system.
Must pricing be fully automated?
No. A merchant can auto-quote, prepare a calculated draft for review, or produce a structured RFQ for manual pricing.
Can each merchant use different pricing logic?
Yes. Merchant schemas, rules and custom tools keep business logic distinct without forking the core runtime.
Do customers need to install anything?
No. Customers continue to send email, messages and files through the channels they already use.
Does AI create orders automatically?
AI proposes an extraction or action. OrderRail checks schemas, rules, permissions and approval policies before execution.
Start with one real workflow
Put your order intake on rails.
Start with one product line and one real workflow.