These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Delivery Slot Management
- Data model and import order
The tables behind Delivery Slot Management
Delivery Slot Management ships with 29 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 29
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Catalog:
Catalogs, product categories, Products, product variants and Collections identify the sellable range.
Basket and customer:
Resources, Addresses, Carts and cart items hold identity and selections before purchase.
Orders:
Bookings and booking resources retain the placed order and its line items.
Money:
Payment methods, payment evidence, tax rates, discount rules, applied discounts and order refunds record configuration and outcomes.
Fulfillment:
Inventory, shipping methods and order shipments connect stock and outbound parcels.
Engagement:
Store sessions, abandoned carts, customer wishlists, product reviews and emails sent retain visitor and service context.
Every table, by feature
- Storefront catalog5
- Carts and checkout8
- Orders and payment6
- Inventory and shipping6
- Customer service6
- Promotions and traffic7
- Shared and settings2
- Catalogs
A record is a storefront setup for a market, letting the team manage currency, language, and region separately.
- Product categories
A record is a grouping used to organize products, helping customers and staff browse by type.
Linked to Product categories - Products
A record is one item the business sells, used to manage what's listed, its details, and whether it's published.
Linked to Catalogs, Product categories - Product variants
A record is one specific version of a product, like a size or color, tracked for pricing and stock.
Linked to Products - Collections
A record is a curated group of products, used to organize what's shown together on the storefront.
- Carts
A record is a shopper's in-progress basket, letting the team track what people are about to buy before they check out.
Linked to Catalogs, Store sessions, Resources - Cart items
A record is one item sitting in a shopper's basket, used to see what they've added before booking.
Linked to Product variants, Carts - Addresses
A record is a delivery or billing address, kept so bookings and shipments use the right location.
Linked to Resources - Shipping methods
A record is a delivery option offered at checkout, used to manage carriers, cost, and how long delivery takes.
Linked to Catalogs - Payment methods
A record is a way customers can pay, used to control which payment options are offered and how they're processed.
Linked to Catalogs - Tax rates
A record defines the tax rate for a region, so staff can use the applicable rate when calculating tax.
- Discount rules
A record defines one discount or promo code, used to control who qualifies and how much they save.
- Config validation runs
Checkout configuration validation runs produced by the Pricing, tax, shipping, payment workflow. One row per validated configuration set; validation never mutates the merchant configuration.
- Bookings
A record is one customer order, used by the team to manage payment and fulfillment status.
Linked to Catalogs, Shipping methods, Resources, Carts - Booking resources
Each row is one item in a booking, so staff can see exactly what was ordered and its quantity, price, and status.
Linked to Product variants, Bookings - Payment evidence
A record is proof of a payment attempt, used to confirm charges went through and to investigate disputes.
Linked to Bookings, Payment methods - Operation receipts
A record logs one event that happened on a booking, giving the team an audit trail of what changed and who did it.
Linked to Bookings, Users - Applied discounts
A record shows a discount actually used on a booking, used to see the savings applied to each order.
Linked to Discount rules, Booking resources, Bookings - Resources
A record is one customer, used to manage their contact details, order history, and marketing preferences.
- Inventory
A record tracks how much stock of an item is on hand at a location, used to check available stock for a variant.
Linked to Product variants - Product variants
A record is one specific version of a product, like a size or color, tracked for pricing and stock.
Linked to Products - Booking resources
Each row is one item in a booking, so staff can see exactly what was ordered and its quantity, price, and status.
Linked to Product variants, Bookings - Order shipments
A record tracks a delivery going out for a booking, used to follow its carrier, tracking, and status.
Linked to Bookings, Shipping methods - Shipping methods
A record is a delivery option offered at checkout, used to manage carriers, cost, and how long delivery takes.
Linked to Catalogs - Bookings
A record is one customer order, used by the team to manage payment and fulfillment status.
Linked to Catalogs, Shipping methods, Resources, Carts
- Resources
A record is one customer, used to manage their contact details, order history, and marketing preferences.
- Addresses
A record is a delivery or billing address, kept so bookings and shipments use the right location.
Linked to Resources - Bookings
A record is one customer order, used by the team to manage payment and fulfillment status.
Linked to Catalogs, Shipping methods, Resources, Carts - Operation receipts
A record logs one event that happened on a booking, giving the team an audit trail of what changed and who did it.
Linked to Bookings, Users - Order refunds
A record is a refund issued on a booking, used to track why it happened and whether it's been processed.
Linked to Bookings, Users - Product reviews
A record is one customer review of a product, used to manage feedback and moderate what's shown publicly.
Linked to Bookings, Products, Product variants, Resources
- Discount rules
A record defines one discount or promo code, used to control who qualifies and how much they save.
- Applied discounts
A record shows a discount actually used on a booking, used to see the savings applied to each order.
Linked to Discount rules, Booking resources, Bookings - Abandoned carts
A record is a basket someone left without booking, used by the team to follow up and win the booking back.
Linked to Carts, Resources, Bookings - Carts
A record is a shopper's in-progress basket, letting the team track what people are about to buy before they check out.
Linked to Catalogs, Store sessions, Resources - Store sessions
A record captures one visit to the store, helping the team see where traffic comes from and whether it converts.
Linked to Resources - Emails sent
A record is one email sent to a customer, used to confirm what went out and whether it was opened.
Linked to Abandoned carts, Resources, Bookings - Customer wishlists
A record is a product a customer saved for later, used to spot interest and follow up on restocks or price drops.
Linked to Resources, Products, Product variants
Keys and references
Keep catalog, product and variant identity stable when importing. A cart item references a variant and a cart; a booking resource references a booking. The booking references its catalog, shipping method and shipping address. Payment evidence, shipments, refund requests and operation receipts refer back to the booking. Reconcile monetary amounts within their currency and keep provider references with the corresponding event.
Migration order
- Load Users, Catalogs and product categories, then Products, product variants and Collections.
- Load shipping methods, payment methods, tax rates and discount rules; review configuration for the intended market.
- Load Resources and Addresses, followed by Carts and cart items when open baskets are part of the cutover.
- Load Bookings and booking resources with original identifiers, then payment evidence, order shipments, order refunds and operation receipts.
- Reconcile opening Inventory, booking totals, payment evidence and parcel states before accepting new orders.
Set up Delivery Slot Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.