Order confirmation

General process

The order process needs a customer legitimation. This was previously done by email, phone calls and fax replies. Both sales person and customer had experienced media breaks and delays.

The current process is completely browser-based. Customers receive an email containing a unique (token based) confirmation link. Opening that link leads to a (shop) web page showing all order details.

From this page the customer has several choices:

• Reject the order, optionally requesting modifications.
• Confirm the order.
• Optionally agree to the "reference" process.
• Optionally choose and perform a payment.

Payment may or may not be available as synchronised online process. For example, "invoice" and "prepaid" payment methods need further communication and are not completely covered within the order confirmation web service.

"Credit card" payment is handled by a payment provider, and the process is completely embedded into the order confirmation page.

Shop process

The order confirmation page is embedded into the shop service. It relies upon data owned by shop, specifically the table shop.gshop_myGiffits_vorgaenge.

Orders are only valid until a certain age, currently 30 days. The shop first finds the order by the incoming token, evaluates its validity and determines a list of allowed payment methods.

Order details are presented to the customer.
After form submission and successful processing the results (confirmed, paid etc.) are written back to the database.

An internal job periodically checks for unprocessed states in the database, pulls them to an internal database and triggers continuation of the sales process.