Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Inventory Management Table.
Required content and structure
Show product variants, stock locations, availability and replenishment notes.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm white, ink text and restrained mint selected states; generous spacing and simple controls. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Supply products, variants, locations, stock quantities, reservations and replenishment notes. Define the relationship between on-hand, reserved and available stock.
Layout and behavior
Keep variant and location context attached to every quantity. Summaries should help identify shortages while making it possible to inspect the records behind a total.
Task-specific acceptance check
- Keep reserved stock distinct from available stock.
- Test one variant at several locations, negative adjustments and reserved stock.
- The interface must not offer reserved units as available merely because they are physically on hand.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Inventory Management Table. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Show product variants, stock locations, availability and replenishment notes. Use the following task-specific layout guidance when translating the image into editable elements: Keep variant and location context attached to every quantity. Summaries should help identify shortages while making it possible to inspect the records behind a total.
Visual direction from the example brief
warm white, ink text and restrained mint selected states; generous spacing and simple controls.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Show product variants, stock locations, availability and replenishment notes. Keep reserved stock distinct from available stock. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write an Inventory Management Table Design Prompt
Use this inventory management table design prompt to show product variants, stock locations, availability and replenishment notes.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Distinguish Stock from Availability
An inventory dashboard should not use one number for on-hand, reserved and available units.
Location and variant are part of the stock identity, not optional decoration. Keep variant and location context attached to every quantity. Summaries should help identify shortages while making it possible to inspect the records behind a total.
From the Prompt
Keep variant and location context attached to every quantity.
Make It Your Own
Group [PRODUCT_VARIANTS] by [LOCATION]. Show on-hand, reserved and available quantities separately, with replenishment notes attached to the relevant variant.
Prepare the Inventory Management Table Content
The stock table groups variants under each product and records a location for each row. Prepare SKU and location keys so stock is not accidentally combined across variants.
Supply products, variants, locations, stock quantities, reservations and replenishment notes. Define the relationship between on-hand, reserved and available stock.
From the Prompt
Show product variants, stock locations, availability and replenishment notes.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this inventory management table. Supply products, variants, locations, stock quantities, reservations and replenishment notes. Define the relationship between on-hand, reserved and available stock. Identify missing inputs before replacing them with demonstration content.
Check a Reserved Item
The right columns distinguish available and reserved amounts from total stock and reorder rules. Verify the arithmetic and thresholds before triggering replenishment actions.
Use an item whose on-hand quantity is positive but fully reserved. It should not appear available for a new order, and switching locations should not hide the reservation. Test one variant at several locations, negative adjustments and reserved stock. The interface must not offer reserved units as available merely because they are physically on hand.
From the Prompt
Keep reserved stock distinct from available stock.
Make It Your Own
Review the inventory management table against this requirement: Keep reserved stock distinct from available stock. Test one variant at several locations, negative adjustments and reserved stock. The interface must not offer reserved units as available merely because they are physically on hand. Preserve approved content and revise only the parts that fail this check.
Review Your Inventory Management Table Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Test one variant at several locations, negative adjustments and reserved stock. The interface must not offer reserved units as available merely because they are physically on hand.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current inventory management table. Test one variant at several locations, negative adjustments and reserved stock. The interface must not offer reserved units as available merely because they are physically on hand. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
