Skip to end of banner
Go to start of banner

Order Features

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

ORDERS

Issue Key

Summary

Description

Issue Type

Release

V5-1449

Include operational details in Order fulfilment Web API

Include operational details of an organisation's opening hours in Order fulfilment Web API

Improvement

V5-1448

Include creatives in Get Order Web API

Include product creatives in Get Order Web API for the ordered items

Improvement

V5-1434

Ability to specify different payment methods for each supply method

Improvement

5.4.1.0

V5-1401

Coverage with map coordinates

Ability to define delivery coverage via coordinates on a map (define map area)

New Feature

5.4.3.0

V5-1388

Ability to retrieve product dependencies during the ordering

Ability to retrieve product dependencies on purchasing a termed service. Any required services or physical goods are provided so as to also be included in the order prior to checkout

Improvement

5.4.0.0

V5-1384

Exclude expense and usage services from orders

Usage and Expense services must be excluded from the ordering process since they cannot be purchased. Expenses are applied based on business rules, whereas Usage service is consumed through one-time/termed services

Improvement

5.4.0.0

V5-1334

Filter Promotions based on organisations

Filter Promotions based on organisations

Improvement

5.4.0.0

V5-1305

Ability to specify the amount to be used from wallet funds

Ability to specify the amount to be used from wallet funds

Improvement

5.4.0.0

V5-1304

Enhance Order details report supporting multiple payment methods

Order details report should be enhanced to support multiple payment methods when multiple payment methods are applied to an order purchase

Improvement

5.4.3.0

V5-1295

Products / Orders

  1. Products should be able to be created at Merchant Level

  2. Products List with param fulfilled_by should use Products at Merchant Level

  3. Orders should be visible at the Business Level and merchant Level of fulfilled_by

Improvement

5.3.5.0

V5-1285

Ability to re-print order ticket

Orders will be marked as printed if printing is successful. the icon in summary screens will show which orders were printed

Improvement

5.3.5.0

V5-1268

Enhance /estimate/orders Self-Service and Back-Office APIs according to spec

Enhance /estimate/orders Self-Service and Back-Office APIs according to spec

Improvement

5.4.1.0

V5-1254

Orders display mode configuration

Users should have the ability to set display mode on the orders page once and each time user visits the page to have the mode of their preference. 

Improvement

Candidate Features

V5-1228

Ability to auto-refresh Orders summary page

Ability to auto-refresh Orders summary page

Improvement

5.4.0.0

V5-1221

Enhance /estimates/orders apis to consider selected payment method for promotions

Enhance /estimates/orders APIs to consider selected payment methods to apply for promotions

Improvement

5.3.4.0

V5-1204

Enhance Self-Service POST /orders API to re-calculate estimated delivery/pick-up time

Enhance Self-Service POST /orders API to re-calculate estimated delivery/pick-up time.

Improvement

5.3.4.0

V5-1117

Ability to accept contact's current location (address, coordinates) and display in Orders

Enhancement to Self-Service /estimates/orders and /orders/\{id} APIs

Improvement

5.3.4.0

V5-1021

Enhancements on order taking to handle product characteristics

Handle API and UI. Characteristics are billing period, trial period, termed period

Improvement

5.4.1.0

V5-826

Fulfilment Policy Enhancements - Expiration of Orders

Improvement

Candidate Features

V5-778

Improved UI for Orders

Enhancements to back-end UI for Orders

Improvement

5.3.0.0

V5-760

Automatically update Orders to Complete status

Ability to configure to automatically set order status to Completed when X time (minutes, hours, days) has passed after Ordering average completion time.

Improvement

5.2.4.0

V5-713

Ability to set preferred venue/merchant for order delivery

  1. The ability for Contact to set the preferred merchant

  2. Enhance /estimates/order_fulfillment API to return a list of merchants/venues that can fulfil contacts' orders sorted by nearest to the contact's selected address

Improvement

5.2.3.0

V5-673

Enhancements to the Order screen

  1. Add the following fields in the Order screen: Contact Code, Contact phone (CIM), Venue Name, Payment method (Cash / Card)

  2. API enhancements required

Improvement

5.2.1.2

V5-672

Add Notes to the bottom of the printed Order ticket

Add Notes to the bottom of the printed Order ticket under Total Items.

Improvement

5.2.1.2

V5-481

Activities for Orders

Activities that need to be scheduled to complete an order (e.g. installation).  

Story

V5-480

Clone an Order

Orders can be cloned, i.e. used as a template for creating additional orders with similar items for a different contact.

Story

Candidate Features

V5-476

Setup your Order Milestones

Set up multiple milestones based on payments which are expected to be made to pay off an order in instalments based on the fulfilment policy. When a milestone due date is reached, the billing process will generate an invoice for the necessary payment and identify the milestone as paid when the payment has been received. 

Point of no return
The Point of no Return settings for orders determine if and when a contact can request to cancel an order or any ordered items.

Prior to reaching the Point of no Return (date), all items, including those that may have already been delivered, can be returned to the company, the contact will not be billed, and the order will be cancelled. On the other hand, if the Point of no Return has been reached, then any items that have been delivered cannot be returned - they will be billed and paid for, while any undelivered items will not be delivered nor billed, and the remaining order will be cancelled.

The Point of no return applies while the order is in progress, i.e. once delivery of items begins.

Story

5.4.5.0

V5-475

Orders Fulfilment Policies

A fulfilment policy is set up for an organisation and is, by default, inherited by all of the organisation's members (merchants, subsidiaries, venues etc.) unless a separate policy is set up for a specific member. A different fulfilment policy can be set up for delivery, pick-up and on-site (dine-in). Users can set the minimum cost for an order to be accepted, define how and when orders can be fulfilled, as well as which products can be ordered based on their availability. Charges per supply method can also be defined (e.g. a delivery charge).
Additional add-on times can be set up using the completion rules.

Completion Rules
Completion rules are set up to calculate the estimated time for an order to be completed and can be venue specific. The average time for completing an order can be set along with additional factors that could affect the time required for completion, such as the ordered product, order quantity, number of concurrent orders and the number of pending items to be processed; all the conditions can be based on days and times of the week, therefore, differentiating between peak hours and off-peak hours. 
The completion rules estimated time (if defined) are in addition to the fulfilment policy's estimated time.

Venues Operational Hours
Define whether pickup and delivery are available per venue and set up the delivery and pick-up times for each one. 

Story

5.2.2.0

V5-474

Create and Amend Orders

Orders can be placed by contacts (using an app) or by users of the system. In either case, an order progresses through the various life cycle states until it is either Completed or cancelled. An estimated completion date/time is calculated for each order, and the payment is processed according to the customer's payment method. The system can also identify any overdue orders. If an order is amended prior to reaching the completed or cancelled states, then the total amount will be recalculated. 

Story

5.2.0.0

V5-359

Product Catalogue for Subscriptions

The product Catalogue includes service products that can be purchased by subscribers, as well as expenses which are applied to subscribers in the form of penalties or fees. The product catalogue includes business rules that define how these products should be purchased:

Dependencies between products.

  • Service product requires a device to be provisioned to contacts (technical)

  • Service product requiring another service(s) to coexist on a subscription in order to be purchased by a contact (driven by a company's business rules).

  • Service product that cannot coexist with another service on a subscription (cannot be purchased and delivered by the same subscription)

Tiering of products

  • Product tiers define whether purchasing a service while owning another one constitutes an upgrade, downgrade or switch.

Services Pricing

  • Service products pricing includes a set of terms that includes

    • A service term period (for termed service only)

    • Whether the terms are auto-renewed at the end of the termed period or not

    • The billing cycle

    • A trial period

  • Pricing terms are used to form the subscription's and the subscription service's billing terms on their purchase

Story

5.4.1.0

V5-2084

Ability to dispatch items for an order

Order items are dispatched against an order and result in a stockout transaction. 

Improvement

5.4.5.0

V5-2365

Display the Total before the discount on the order ticket.

Enhance Order ticket to include:
Price of items before the discount
Total Price before discount

Improvement

5.4.5.3

V5-2268

Back-end Ordering enhancement, display modifiers section AFTER a variant product is selected

Display modifiers section AFTER a variant product is selected and based on modifiers of the selected variant product

Improvement

5.4.5.2

V5-2086

New view options for the Orders summary screen

Updates are required to the Orders list view/Kanban view. New Kanban view linked to queue types. New detailed order summary page. 

Improvement

5.4.5.0

V5-2085

Ad hoc discounting 

Ad hoc discounts for Service Requests and Orders. 

Improvement

5.4.5.3

V5-2083

Point of No return

Implement the point of no return for orders. 

Improvement

5.4.5.0

V5-2082

Updates to Orders

Ability to change certain details of an order once an order is created and change order statuses. 

Improvement

5.4.5.0

V5-1986

Include conditions in Order Fulfilment policy expenses

Provide the ability to set up conditions on when an expense will be applied during ordering. Currently, the supply method is already a condition. The order's amount should be added (order amount before the discount)
e.g. apply the expense for Delivery orders only if the order amount is less than X amount

Improvement

5.4.4.1

V5-1981

Include Product Notes in the Order ticket

Notes for orders 

Improvement

5.4.4.1

V5-1797

Enhancement to provide detailed promotion information in invoicing

Include promotion information when invoicing

Improvement

5.4.3.2

V5-1701

Enhance Self-Service Order fulfilment response with an estimated delivery/pickup time

Enhance Self-Service Order fulfilment response with an estimated delivery/pickup time so that order fulfilment checks can be removed from order estimates. Required for mobile app ordering flow

Improvement

5.4.3.1

V5-1685

Ability to create default fulfilment policy upon new Business sign-up. New Direct Sale supply method

A default fulfilment policy will be created when a new Business signs up.
New supply method' direct sale' for subscription services.

Improvement

5.4.4.2

V5-1602

Enhance the order to include whether the order was paid in full or partially with wallet funds

Order enhancement to include the amount partially paid using wallet funds and the amount partially paid using another payment method 

Improvement

5.4.3.1

V5-479

Ability to have Separate Queues for your Orders

Ability to set up different order queues, with each queue having its own workflow of states. Set up the business characteristics of orders to be fulfilled by each queue, for example, B2B orders assigned to the 'Wholesale' queue and B2C orders assigned to the 'Retail' queue.

Story

5.4.5.0

V5-477

Orders Quotation 

A Quotation provides a formal estimation of an order's cost that includes all physical goods, expenses and services that the contact is interested in buying. In other words, the quotation is a preliminary form of the order's invoice

Story

5.4.5.0

V5-476

Orders milestone and progress-based invoicing

Support for invoicing based on preset milestones or based on the progress of delivered services and products.

Story

5.4.5.0

V5-2274

Ability to define on front-end systems whether to allow purchases only if the requested spend amount is fully covered with the available wallet balance

Ability to define on front-end systems whether to allow purchases only if the requested spend amount is fully covered from the available wallet balance.

  • Ability to configure setting via the back-end (Applications)

  • Release app enhancements

Improvement

5.4.5.2

V5-1405

Purchases & Business Network

Posting purchases against an organisation should allow only purchases of organisations within the business network

Improvement

5.4.0.0

V5-2633

Using Wallet funds on order improvement

  • When a contact wants to fully/partially pay for their order using their wallet funds - up to 2 payments will be posted upon placing the order:

  • One payment with payment method type cash/card etc., according to the contact's choice

  • Second payment to reflect the contact's payment using the wallet as a payment method

Improvement

5.4.6.2

V5-2632

Improved use of account funds on placing the order

Improved use of account/wallet funds on placing an order

  • Order estimates API to return

  • Cost of the order 

  • The amount which needs to be paid at the time of ordering

  • Contact's account credit (if the account is credited)

  • On placing the order

  • It will be up to the front end to decide if account credit will be used or not to pay off the order.

  • Up to two payments will be placed, one consuming wallet funds and the second one to represent the payment using a card/cash etc.

  • In cases where the account's credit will be used, then the cash/card payment will be of a smaller value, indicating that the remaining amount will be paid off using the account's funds

Improvement

5.4.6.2

V5-2105

Contact and User approvals for orders

The ability for a contact and/or user to approve/reject an order's progression via CRM.COM Approval Request automation

Improvement

5.4.6.3

V5-2903

Ability to set up automation on order stage change

Ability to set up automation which is triggered upon changing the stage of an order

Improvement

5.4.6.4

V5-3056

Orders & milestones enhancement

Display Order milestones (whether invoiced or not) on the Order screen

Improvement

5.5.0.0

V5-2438

Order Attachments

Ability to add attachments to an order

Improvement

5.5.1.0

V5-480

Clone an Order

Orders can be cloned, i.e. used as a template for creating additional orders with similar items for the same or a different contact.

Story

5.5.2.1

V5-480

Clone an Order

Orders can be cloned, i.e. used as a template for creating additional orders with similar items for the same or a different contact.

Story

5.5.2.2

V5-3622

Search for orders based on their address

Ability to search for an order using its delivery address. A new 'Address' filter option added 

Improvement

5.5.3.2

V5-3416

Ability to change an Order's Delivery address 

Ability to change an Order's Delivery address before its completion. Changing the delivery address is allowed only if no items have been sent out to the contact. Order fulfilment estimation should be triggered again to ensure that the order can still be fulfilled at the new delivery address

Improvement

5.5.3.2

V5-3606

Improved Orders management

Ability to amend order items and milestones provided a point of no return is not reached.

Improvement

5.5.3.2

V5-4295

Ability to set up and use Event-based Charges for Orders

Ability to set up and use Event-based Charges for Orders. In addition, introduce the ability to charge an extra expense on a delivery Order based on the distance

New Feature

5.6.0.0

V5-4287

Product Ordering & Commerce Spend Restrictions

Ability to support (per product) the max wallet commerce amount that can be spent during ordering

Improvement

5.6.0.0

  • No labels