From catalogue to order.With your confirmation rules.
Start with ready-to-use management software for products, orders and bookings. Then work with Shappy to adapt the information you collect, preparation stages and connections your company needs.
An order continues beyond the form.
Julie prepares the week’s orders and workshops. She matches requested references, quantities and available places.
- 01
Prepare the catalogue
Describe products and variants with prices in euros. Slots keep an explicit capacity.
- 02
Follow requests
Keep customer, order lines and expected date in an identifiable record.
- 03
Check confirmation
Check the order total and slot capacity before confirmation. Cancellations retain their context.
Read the offer and its fulfilment together.
These are internal management views. The preview does not publish a storefront or accept real orders.
Requests have a next step.
Follow preparation of a fictional order. No payment, shipment or notification is triggered.
Bookings that fit your offering.
Tell Shappy what needs to change. Watch your software take on your way of working.
Your software, your rules
Add participant experience level to workshop bookings and a preparation view by slot for the welcome coordinator.
Watch the transformation
Take this example for a spin.
Switch views, open a record and try the available actions. Linked records show how the workflow fits together.
Choose how orders enter your workflow.
The public website, payment and preparation are separate workflows. Each needs connection and verification.
- Your website or forms
Customer, request, item reference and requested time slot.
What is needed : Define the receiving interface, validation and duplicate handling. This preview is not a published storefront.
- Authenticated customer portal
Orders and bookings belonging to the signed-in customer.
What is needed : A manager links the Core identity to the customer and configures roles. No public portal or access to every record is claimed.
- Stock and payment provider
References to prepare and transaction reference to match to an order.
What is needed : Verify authorised connections, payment provider and return handling. No active PayPal connection or native collection is claimed.
Walk through an order and a booking.
- 01
Choose the offer
An item, a slot and their terms give a concrete initial scope.
- 02
Define confirmations
Define what reserves, cancels, prepares or confirms in your business.
- 03
Adapt, then connect
Tell Shappy what information and preparation rules you need. Check the changes, access and external transfers before any public launch.
Your questions before choosing your software.
Can we adapt the workflow to our offering?
Yes. Product, order and booking management provide the starting point. Evolve your software with Shappy to add customer information, preparation stages or confirmation rules. Changes and any connections to your website are checked before release.
Does this preview publish a store?
No. The scope includes neither a public storefront nor a CMS. It covers products, orders, bookings and an authenticated customer portal to configure.
Can we collect payments with PayPal?
No active PayPal connection is claimed here. The provider, access and transaction lifecycle must be verified before promising payment collection.
What happens when a slot is full?
The preview blocks another place beyond capacity. Concurrent bookings, cancellations and actual confirmations are validated in the application.
Does the software manage stock and shipping?
The scope does not include physical stock, logistics, taxes or fiscal invoices. A connection to another application must be defined and authorised separately.
Your offering deserves its own workflow.
Start with a customer request and the existing software to define the information, approvals and connections your company needs.
Bring a representative record and your working rules. We will define data migration and the first changes to check.