Orders you can trust eight months later · Data Modeling scenario

Preparing your workspaceloading the brief, studio & canvas…

Loadingone moment…

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined Shoply. Prices change constantly, products get renamed, and discontinued products disappear from the catalogue entirely — while support needs to open an order from eight months ago and see exactly what the customer saw and paid. The checkout page also double-submits when somebody taps Pay twice on a slow connection.

your model must answer

01A customer's order history, most recent first?
02Everything on one order, exactly as the customer saw it at purchase?
03Create an order such that a double-submit cannot produce two orders?

out of scopeReturns · promotions · tax · carriers · stock levels

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.Orders you can trust eight months later

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01A customer's order history, most recent first?
02Everything on one order, exactly as the customer saw it at purchase?
03Create an order such that a double-submit cannot produce two orders?

out of scopeReturns · promotions · tax · carriers · stock levels

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.Orders you can trust eight months later

Design review

The reviewer reads your model.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Orders you can trust eight months later · Data Modeling scenario · D8LooP