Marketplace · United States
Keystone unified sellers, payments, and support so Friday payout recon stops being a war room.
Multi-seller marketplace · growth stage
Executive summary
We tried three tools that looked pretty. CEDX is the one the team still uses on Friday.
The challenge
Three vendors meant three truth sources. Friday meant reconciling who got paid.
Support could not see seller policies. Sellers could not see ticket state.
Pretty tools died after the pilot because ops refused to live in them.
Stack change
What the team stopped using - and what runs on CEDX.
The change
Marketplace, Catalog, Payments, Orders, and Desk on one estate.
Sellers see the same order state as support.
Payments reconcile against the order, not a side sheet.
Outcomes
Results used as pilot targets - the shape of success, not vanity dashboards.
Team impact
One stack the team still uses Friday.
Policies and tickets on the same record.
Payout recon without three CSVs.
Why an estate
Sales, service, and finance stop arguing about whose record is authoritative.
Operators do not maintain six passwords and six partial truths.
What you evaluate on the website is the build you implement.
Start with one motion; add products without a second platform.
Rollout
Typical shape - your pilot may compress or expand by product footprint.
Catalog + Marketplace
Seller onboarding.
Orders + Payments
Payout truth.
Desk
Support on the same order.
Grow
No tool swap mid-scale.
Risks
Your next 90 days
Same skeleton Harbor, Northline, and Atlas-shaped programs use.
Estate map
Sponsor, operators, systems list, retire list, pilot metrics.
Pilot live
One pod or region on production-shaped config.
Expand wave
Second region or adjacent product family.
Hypercare exit
Metrics review, owner map, BAU support path.
In the room
Keystone Markets runs day-to-day work in CEDX - the same apps you can open from every product page.
FAQ
It is an illustrative composite on live demo tenants. Named case studies publish with customer approval.
Yes. Products in this scenario: Marketplace, Catalog, Payments, Desk, Orders.
CEDX, a consulting partner, or both - decided in the estate map.
Architecture notes
One login for operators in scope. Entitlements follow the product graph.
Customer graph ownership is written in the estate map before imports.
Prefer estate events and first-party connectors over brittle nightly CSV.
Commercial shape
Products in the first motion, seats for the pod, success metrics, hypercare window.
Wave-two products and regions after metrics clear - written in the original map when possible.
Related scenarios
Harbor put POS, CRM, inventory, and desk on one login so store close and support share the same customer.
B2B servicesNorthline collapsed six tools into one estate so new reps quote, sign, and bill on the same customer graph.
LogisticsAtlas put field jobs, parts, and contact-center voice on one desk record across three provinces.
Thirty minutes. Products, retire list, and pilot metrics - before anyone configures.
