Feature / Process | Description |
---|---|
Orders | Orders placed by contacts (B2C/B2B contacts) to purchase physical goods and services offered by the business or the business’s merchants in its business networkits merchants/B2B Merchants within the Business Network. An Order is fulfilled by either the business or one of the merchants/venues in order of the following methods:
An Order follows a Queue that defines its
An Order is considered as completed when:
|
Order fulfilment estimates | Indicates if and which organisation (merchant or venue) will fulfil a contact’s delivery/pick-up order before the contact reaches the checkout screen |
Order estimates | Provides an estimation on if, when how the order will be fulfilled and by which merchant/venue, plus the order’s detailed amounts
Order estimates amounts can be used for issuing a quotation to the contact. |
Milestone-based vs. Progress-based | An Order can be paid off using various models:
The Order’s final invoice is issued upon its completion. In the final invoice, the Milestone invoices are credited. |
Placing the order | Contacts specify the order’s basic information, which is:
Order estimation Web APIs are utilised throughout the ordering flow
Placing the Order is based on a key attribute; the estimation_id, which encapsulates the order’s details (valid for 2 hours) Another t important input is the order’s payments:
|
Subscription Orders | Contact willing to subscribe to new services follow the standard ordering flow in order to view a list of services that they can subscribe to as well as their price terms. Order estimation, in this case, additionally includes
On placing the Order, all ordered services are added to the contract, subscriptions are created/existing ones are amended with the new services. As a result, the Order is also automatically completed since the services are delivered to the contact. In addition, the Service Delivery process is the one responsible for billing the subscriber for the ordered services. |
B2B Marketplace Orders | Business aggregates products from its B2B Merchants and allows its contacts to place orders through the business’s marketplace. Contacts can place orders and include products from one or more B2B Merchants. Multiple orders are created, one for each B2B Merchant that is responsible for fulfilling the order. |
Milestones |
|
Point of no Return | The point in time (during an Order’s processing) up until which contact can cancel the order.
An Order’s PoNR is defined in one of the Queue’s stages. |
When can a contract change or cancel the order | An order can be changed or cancelled at any point in time, but some restrictions are applied.
|
Automations | Complete list of automation that enables
|
Approvals | Set-up approvals enable the business to progress an order only after the contact and/or a user approves the progression. Approvals available through Automations. |
Event-based Charges | Set-up event-based charges to be applied on placing an Order. More specifically, apply either a standard fee (i.e. an expense whose price is retrieved from the Product Catalogue) or apply an expense whose final price depends on the distance between the venue (the organisation that fulfills the order) and the contact’s delivery address. |
Order Catalogues | Ability to group/categorise items in the product catalogue with the purpose of easily presenting them to contacts 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. |
Page Comparison
General
Content
Integrations