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.
- Click & Collect System
- Data model
The tables behind Click & Collect System
Click & Collect System 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
Every table, by feature
- Catalog and merchandising5
- Cart and customer activity6
- Orders and service5
- Payment and pricing6
- Inventory and fulfillment5
- Returns and engagement5
- Shared and settings2
- Catalogs
Each record is a storefront or sales channel, used to manage products and settings per market.
- Products
Each record is a product sold in the store, used to manage listings, descriptions, and status.
Linked to Catalogs, Product categories - Product variants
Each record is a specific version of a product, like a size or color, used to manage pricing and stock.
Linked to Products - Product categories
Each record is a grouping used to organize products so customers can browse the catalog easily.
Linked to Product categories - Collections
Each record is a curated group of products, used to feature or organize items for shoppers.
- Store sessions
Each record is one visit to the storefront, used to see where shoppers come from and how they browse.
Linked to Customers - Carts
Each record is a shopper's in-progress cart, used to track what they're about to buy before checkout.
Linked to Catalogs, Store sessions, Customers - Cart items
Each record is one product added to a cart, used to see what a shopper is planning to buy.
Linked to Product variants, Carts - Abandoned carts
Each record is a cart a shopper left without buying, used to follow up and try to recover the sale.
Linked to Carts, Customers, Customer orders - Customers
Each record is a person who has shopped or signed up, used to manage contact info and order history.
- Customer wishlists
Each record is a product a customer has saved for later, used to see what shoppers want to buy.
Linked to Customers, Products, Product variants
- Customer orders
Each record is a completed order placed by a customer, used to track what was bought and its status.
Linked to Catalogs, Shipping methods, Customers, Carts - Order lines
Each record is one item within an order, used to track what was ordered, shipped, and billed.
Linked to Product variants, Customer orders - Order events
Each record is a logged action or update on an order, used to trace what happened and when.
Linked to Customer orders, Users - Addresses
Each record is a shipping or billing address, used to know where to send orders and invoices.
Linked to Customers - Customers
Each record is a person who has shopped or signed up, used to manage contact info and order history.
- Payment methods
Each record is a way customers can pay, used to configure which payment options are offered.
Linked to Catalogs - Payment evidence
Each record is a captured payment attempt or charge, used to confirm and audit how an order was paid.
Linked to Customer orders, Payment methods - Tax rates
Each record is a tax rate for a region, used to charge the correct tax on orders.
- Discount rules
Each record is a discount or promotion, used to define how and when customers get a price break.
- Applied discounts
Each record is a discount actually applied to an order, used to track savings given to customers.
Linked to Discount rules, Order lines, Customer orders - 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.
- Inventory
Each record is the stock level of a product at a warehouse, used to know what's available to sell.
Linked to Product variants - Order shipments
Each record is a shipment sent for an order, used to track delivery status and tracking info.
Linked to Customer orders, Shipping methods - Customer orders
Each record is a completed order placed by a customer, used to track what was bought and its status.
Linked to Catalogs, Shipping methods, Customers, Carts - Order lines
Each record is one item within an order, used to track what was ordered, shipped, and billed.
Linked to Product variants, Customer orders - Shipping methods
Each record is a delivery option, used to configure shipping choices, cost, and speed for customers.
Linked to Catalogs
- Order refunds
Each record is a refund issued for an order, used to track money returned to customers.
Linked to Customer orders, Users - Product reviews
Each record is a customer review of a product, used to gauge feedback and build trust with shoppers.
Linked to Customer orders, Products, Product variants, Customers - Emails sent
Each record is an email sent to a customer, used to track communications like receipts and updates.
Linked to Abandoned carts, Customers, Customer orders - Abandoned carts
Each record is a cart a shopper left without buying, used to follow up and try to recover the sale.
Linked to Carts, Customers, Customer orders - Customer orders
Each record is a completed order placed by a customer, used to track what was bought and its status.
Linked to Catalogs, Shipping methods, Customers, Carts
Keys and references
Use the catalog code, variant SKU and order record number as operational identifiers. Preserve reference links when importing records so an order line resolves to its variant and a shipment or refund resolves to its order. Check currency and catalog on sample orders before loading a larger history.
Migration order
- Load catalogs, categories, products and variants.
- Load customers and addresses, then payment, shipping and tax configuration.
- Load carts, customer orders and order lines.
- Load inventory, shipments, payment evidence, refunds and event history.
- Reconcile discounts, reviews, sessions and communication records.
Set up Click & Collect System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.