Turn every purchase into work your team can follow.
Create and manage orders with the customer, items, pricing, currency, channel, fulfillment, and change history kept in one record. For tours and airport transfers, keep each booking tied to the order item that created it.
Give every order enough context to stand on its own.
An order should show more than what was purchased. Wexcy preserves the customer, items, commercial values, and operational context that teams need to understand and continue the work.
What the order carries
Customer snapshot
Retain the relevant customer identity and shipping or billing address details with the order.
Item snapshot
Record product variants, bundle relationships, or supported service items as they were placed.
Commercial values
Keep currency, subtotal, discounts, shipping, tax, adjustments, grand total, and base-currency context explicit.
Operational context
Preserve order number, channel, source, notes, timestamps, and the history of state changes.
A lifecycle the team can read
Make the next order step easy to see.
The main path stays clear, while cancellation remains a controlled branch with its own history.
01
Draft
Prepare or revise the order before placement, and run the relevant pre-place checks.
02
Placed
Commit the customer, item, pricing, currency, and channel context to the order.
03
In progress
Show that the responsible team has begun operational work.
04
Completed
Close the order through the implemented completion rules.
Three views of the same order
Track order progress, payment, and fulfillment separately.
These three tracks follow different rules. Keeping them separate helps the team read the order correctly instead of inferring one state from another.
Order
Draft · Placed · In progress · Cancelled · Completed
Financial
Pending · Collected · Cancelled
Fulfillment
Unfulfilled · Fulfilled
Commercial context that stays explainable
Know how the total was formed—and why it changed.
Wexcy records the values that shape an order and can retain pricing comparisons or justifications when a draft is reviewed or an exchange-rate snapshot changes.
Transparent totals
Keep subtotal, discount, shipping, tax, adjustment, and grand-total components distinct.
Currency snapshot
Retain the order currency, base currency, rate, quote direction, and provider context represented by the record.
Revision context
Use pricing revisions, comparisons, and justification records to explain a deliberate difference.
Notes and history
Give teams a durable place for order notes and recorded state changes.
Service detail without a disconnected record
Keep each service booking tied to the order that created it.
For private tours, shared tours, and airport transfers, the booking record remains connected to its order and order item while preserving the service details the operating team needs.
Private tour
Scheduled date and time, passenger count, optional vehicle category, traveler context, luggage, add-ons, and notes.
Shared tour
Departure, adult, child, and infant counts, consumed seats, traveler context, luggage, add-ons, and notes.
Airport transfer
Pickup and drop-off places, schedule, passenger count, optional vehicle category, traveler context, luggage, add-ons, and notes.
A clearer handoff
Hand the next team a usable record, not scattered clues.
The order brings together the context produced by customer experience, catalog, pricing, and inventory work. The next responsible team can inspect the recorded decision before fulfillment or service delivery continues.
owns applicable warehouse balances, reservations, movements, and consumption
Orders & Bookings
owns the commercial order record and supported booking records tied to its items
Orders and booking questions
What to know before your team manages purchases and service records.
Clear answers about order context, draft review, state, pricing, product items, supported bookings, and connected responsibilities.
It can retain the order number, customer and address snapshots, item details, channel and source, payment method, currency and exchange context, totals, notes, timestamps, and state history.
Yes. Your team can create and edit a draft, clone an order into a new draft, run the relevant pre-place check, and then place it through the implemented rules.
No. They are separate tracks: operational progress, financial state, and fulfillment state each follow their own rules and should be read independently.
Yes. An order can represent product-variant items and preserve bundle parent and component relationships in its item snapshot.
An order can include private tours, shared tours, and airport transfers as supported booking records tied to an order item.
The record can keep its schedule, traveler contact, passenger and luggage counts, relevant vehicle or location details, add-ons, notes, booking number, and timestamps.
No. Booking confirmation is separate from the order’s financial state, so the team should review each fact independently.
No. Those amounts can be recorded as pricing components, while carrier shipping and tax-calculation services require independently verified implementations or integrations.
Start with a clearer order record
Give every purchase a context your team can continue.
Bring the customer, items, commercial values, operational state, and supported booking detail into a record built for the next responsible action.