E-commerce use case - ShapeKit | ShapeKit
E-commerce
Let warehouse, finance, and CS see orders their way.
You built one order management system. The warehouse team needs fulfillment status. Finance needs payment and refund tracking. CS needs customer history. Build once, stop reshaping it for everyone else.
Ridge & Pine Order operations
| Order | Customer | Fulfillment | Payment | Total | Placed |
|---|---|---|---|---|---|
| #10482 | M. Okonkwo, Lagos | Picked | Paid | $184.20 | 12 min ago |
| #10481 | S. Ravensbourne, NYC | Awaiting | Refunded | $92.50 | 38 min ago |
| #10480 | H. Linnstrom, Oslo | Shipped | Paid | $418.00 | 1h ago |
| #10479 | A. Vance, Toronto | Picked | Paid | $67.80 | 2h ago |
| #10478 | D. Park, Seoul | Shipped | Paid | $249.95 | 3h ago |
Awaiting
#10481
$$92.50 Awaiting
Picked
#10482
$$184.20 Picked
#10479
$$67.80 Picked
Shipped
#10480
$$418.00 Shipped
#10478
$$249.95 Shipped
One order app. Warehouse, finance, and CS each shape their view.
The problem
Your order management system tracks everything: products, customers, payments, fulfillment, returns. But each team sees the same data differently. You end up building custom dashboards and admin views for everyone. Then you maintain them. Then they ask for changes.
How it works
1. Warehouse team reshapes for fulfillment
They see incoming orders, pick lists, packing status. They hide payment details, customer emails, anything they don't use. They get the view that matters for their work.
2. Finance team reshapes for accounting
They see revenue by date, refunds, payment methods, tax. They reshape to match their ledger. They focus on what they need, not on tracking statuses they don't care about.
3. CS team reshapes for customer context
They see all orders for one customer, status timeline, return history. They reshape to show what matters when talking to someone on the phone. No digging through noise.
What you build
Orders
Line items, totals, status tracking. One table.
Products
SKU, inventory, pricing. One schema.
Customers
Contact, purchase history, addresses. One source.
Payments
Method, amount, refunds, disputes. Unified.
What changes for each team
Same data, different shapes. Your teams describe what they need, and they get it.
Warehouse
- Filter by fulfillment status
- Sort by order date
- Hide payment data
- Add pick list columns
Finance
- Group by payment method
- Show refunds separately
- Hide order tracking
- Add tax columns
Customer Service
- Filter by customer
- Show order timeline
- Hide payments/inventory
- Track returns
What happens next
Each team builds their view without asking you. No dev work. No meetings about columns. You see which views are actually used and what your teams care about most.
Stop building custom dashboards for every role.
Ship your order system. Let your team reshape it.