Through _cpanel/checkout-settings, provide store owners using Managed Checkout with greater options for customising their checkout:
a) No limits on required delivery date:
At the moment, it isn?t possible to put a limit on how far in advance a customer can request a Required Delivery Date.
This can mean customers are able to order products which may not be available in future; or order them at a price which puts either the customer (or the business themselves) at a disadvantage.
b) No ability to enforce various fields being required (i.e. Preferred delivery date):
Where a business using Neto (i.e. in the grocery/liquor vertical sector) performs deliveries themselves, or allows customers to schedule deliveries in advance - there is no way for them to ensure the customer tells them in checkout when they want the order to be delivered (either date, and potentially time).
To resolve any missing information of this nature requires additional administrative work on their part, following up with customers who?ve left this field blank.
c) No ability to turn off features the store doesn?t need at checkout:
Following on from (a), if a store only allows customers to place orders seven (7) days in advance, the ?Set future reminder for this event? field is redundant.
There is no way for the store owner to switch this off.
d) No methods for API integration (Address Matching and Verification; Document Verification):
At present, the Managed Checkout doesn?t allow any form of integration or use with API?s or other such technologies for the purpose of confirming the customer has entered and selected a valid address.
If you were only delivering to Australians, and you don?t accept PO Boxes, you?d want to be able to validate the address entered, and ensure it was a valid residential delivery address, using an Auspost-approved AMAS real-time provider.
And if you handled liquor, you might want to use an approved Document Verification Service for a customers first checkout to make sure they were over the age of 18 as part of your risk management strategy.
Again, no way available to integrate to do either of these things.
e) Custom order fields do not allow formats beyond text, nor are validation rules supported:
If you needed to capture things such as dates, dates of birth, and the like - there?s no way for you to specify the data entered as a date, let alone validate the data as a date.
As a consequence, more administrative overhead checking things before sending things; meaning less time driving your business.
�
