Order Management Business Features
Feature / Process | Description |
|---|---|
Orders | Orders can be placed by B2C or B2B contacts to purchase physical goods and services offered by the business, its merchants, or its B2B merchants within the Business Network. CRM.COM enables the seamless deployment of multiple co-existing order processes, supporting a wide range of business scenarios:
Order Fulfilment Fulfillment is the process whereby an Organisation (Business, Merchant or B2B Merchant) defines how they fulfill orders placed by contacts by either delivering them or having contacts picking them up. The fulfillment behaviour is defined via a Fulfillment policy that may include coverage, the available supply and delivery methods and possible delivery charges. Each organisation has maximum one fulfillment policy and is reversely hierarchical, meaning that the policy of a merchant takes precedent over that of the organisation (the business). Supply Methods An order may be fulfilled by the business or by a merchant/venue using one of the following supply methods:
Delivery Methods An order with Delivery supply method may have one of the following Delivery Methods that determine the way the items will be delivered to the contact:
Order Queues Each order follows a specific Queue, which defines:
Order Completion Criteria An order is considered ‘Complete’ when:
Users can follow the Order Setup Wizard to configure all aspects of order management, including order processes, financial settings, fulfilment options, and automation rules. |
Order Fulfilment Estimatation | The order fulfilment estimate indicates whether and which organisation (merchant or venue) will fulfil a contact’s delivery or pick-up order before they reach the checkout screen. |
Order Estimates | Order estimates provide a full preview of whether, when, and how an order will be fulfiled, as well as which merchant or venue will handle the fulfilment. They also include a detailed breakdown of the order’s financial amounts, such as:
Order estimate amounts can also be used to issue a quotation to the contact. |
Milestone-based vs. Progress-based | An Order can be settled using several invoicing models:
|
Placing an Order | Order Information Provided by Contacts When placing an order, contacts specify the following core information:
Order Estimation Web APIs Order Estimation APIs are used throughout the ordering flow to:
Placing an order is driven by the estimation_id, which encapsulates all order details and remains valid for 2 hours. Order Payments Orders can be paid using multiple payment methods, such a combination of the CRM.COM Wallet and Card. The payment distribution is calculated based on available account credit and wallet balance. |
Subscription Orders | Subscribing to New Services Contacts who wish to subscribe to new services follow the standard ordering flow, where they can:
Order Estimation for Services In the case of service subscriptions, the order estimation additionally provides:
Order Placement and Subscription Activation When the order is completed:
|
B2B Marketplace Orders | The business aggregates products from its B2B Merchants and enables its contacts to place orders through the business’s marketplace. A single shopping experience can include products from multiple B2B Merchants. When an order is placed, CRM.COM automatically creates separate orders, one for each B2B Merchant responsible for fulfilling its portion of the order. Splitting the Order is based on the product’s owner, so each owner - i.e. B2B Merchant - is responsible for fulfilling the order. |
Milestones |
|
Point of No Return | The Point of No Return (PoNR) is the stage in an order’s processing after which the contact is still allowed to request the order’s cancellation, but they cannot returned the items delivered to them:
The PoNR for an order is defined as part of a specific stage within the order’s Queue. |
Modifying or Cancelling an Order | An order can be changed or cancelled at any time, subject to certain restrictions:
|
Automations | Automations for Orders can be created based on he following events:
Available actions depending on the selected event:
|
Approvals | Approvals can be configured using the automation trigger event 'Approval on Order Stage Change'. This ensures that an order can progress to the next stage only after the required approval has been granted by the contact and/or an authorised user. |
Event-based Charges | Event-based charges can be configured to apply when an order is placed. These charges can be set up in different ways, such as:
|
Order Catalogues | Order Catalogues allow items from the product catalogue to be grouped or categorised for easier presentation to contacts. Items can be organised based on:
|
Analytics | Advanced business intelligence through:
|
Custom Fields | Extend an Order’s information based on Custom Fields defined by the business. |
Custom Forms | Configure your own custom data screen for Orders. This is an external implementation designed using CRM.COM’s Back-Office APIs and hosted outside of CRM.COM, which can be loaded and used via the back-end system. |