Sports & outdoor
Running shoe
Fit, terrain, drop, cushioning, waterproof rating and size conventions.
terraindrop_mmarch_supportFeatures
Set the product details your business actually needs, check every supplier range and approve changes before they affect products, categories, filters or sales channels.
Four connected tools keep planning, review, approval and delivery in sync.
Catalog controls
Governance toolkit
Catalog Architect
The rules stay visible.
Policy coverage
Templates
18 activeRequired fields
Imports
184 stagedReview at entry
Approval
96% validVisible decisions
Delivery
API liveStable contracts
Consistent product information
Approved product details replace duplicate labels and inconsistent wording, keeping filters useful, supplier onboarding clearer and product comparison stronger.
Attribute contract
Each product detail belongs to a product group and has clear approved choices. Teams can see what the catalog means before a website, report or sales tool depends on it.
product.attributes
Trail running shoe
6 / 6 fields validProduct standards
Keep unrelated details out of the way while making required information, approved choices and filter behaviour clear across an entire range.
Sports & outdoor
Fit, terrain, drop, cushioning, waterproof rating and size conventions.
terraindrop_mmarch_supportConsumer electronics
Storage, display, connectivity, camera and operating-system specifications.
storage_gbscreen_innetworkDIY & hardware
Power source, voltage, chuck size, torque and compatible battery family.
voltagechuck_mmbattery_familyCatalog planning
See how categories, product details and supplier ranges fit together. Teams can prepare a strong starting point while the retailer keeps approval of what goes live.
Catalog model
Draft · merchant review required
The durable value is the governed model, not the drafting shortcut. Teams remain responsible for the structure that products and channels will inherit.
Supplier ranges
Match incoming information to your product standards, check it against the right category and keep proposed changes visible until a catalog owner approves, rejects or leaves them for later.
Supplier terminology can be mapped and normalised, but it does not quietly redefine categories, filters or allowed values. Approved changes update the template, increment its schema version and enter the activity history.
Import review
184 product rows staged for review
Template assignment
Denim apparel
Required attributes
14 of 14 supplied
Unknown values
3 mappings or values proposed
Unknown attributes
1 template change proposed
Category assignment
Jeans
Search and filters
StoriTail gives search, filters and merchandising the same approved product details. Keep your existing shopping experience while making the catalog underneath more dependable.
Fragmented input
What the storefront receives
5
separate filter values
0
reliable comparisons
Governed discovery
Colour
Fit
Waist
Matching products
2 exact results · 0 inferredStraight jean
£86
Navy · Regular · Waist 30
Slim jean
£78
Navy · Slim · Waist 30
Filter governance
Filters should follow the way a product is understood, not whichever choices happen to arrive from a supplier. Teams can choose one or several selections for each product detail.
Availability is handled separately. Keeping zero-result choices visible means familiar options do not disappear when a size, colour or specification is temporarily out of stock.
Approve these rules once, then every storefront and discovery surface can apply the same predictable filter logic.
From product rule to reliable navigation
Activity and controls
See which products and supplier ranges need attention, assign reviews and keep a clear record of the decisions that change your catalog.
Activity
Template approved
09:42Denim apparel · 14 attributes
Import review assigned
10:05supplier-denim-range.csv
Category change proposed
11:18Jeans · awaiting approval
Validation complete
11:44184 rows checked · 3 values normalised
Product publication approved
12:03Straight jean · 24 variants
Catalog controls
Connected sales channels
StoriTail makes approved categories, product details and filter rules available to the tools your business already uses, so teams do not have to maintain separate versions of the range.
API Playground
Current workspace · storefront reads
Choose a request
/api/v1/storefront/categories?verticalKey=fashion-apparelThin navigation with template context
/api/v1/storefront/category-filters?templateKey=denim-apparelTyped facets and selection rules
/api/v1/storefront/products?attribute.colour=navyQuery canonical product attributes
/api/v1/storefront/products/straight-jeanStable product detail by ID or slug
200 · JSON response
Live contract{
"data": {
"scope": { "templateKey": "denim-apparel" },
"filters": [{
"key": "colour",
"type": "enum",
"selectionMode": "multi",
"options": [
{ "value": "Navy", "count": 24 },
{ "value": "Stone", "count": 12 }
]
]
,},
"meta": { "beta": true }
}01 · Navigation
Give every channel the same category and product context for browsing.
02 · Discovery
Use approved product details, clear choices and live counts to build useful filters.
03 · Products
Find products by category, price or approved product detail wherever they are needed.
Govern once. Read the same meaning everywhere.
The API exposes the catalog model; it does not create a competing one.
Ready for what comes next
The practical benefits come first: cleaner operations, stronger discovery and reusable product details. New shopping tools benefit because the foundation is already clear.
Operational value now
Clear product standards and supplier checks improve everyday catalog work first.
Shared discovery layer
Search, filters, merchandising and sales tools can use the same approved details.
Downstream readiness
Future shopping tools benefit from clear product information without becoming the reason the catalog exists.
Tools for better catalog decisions
Set product standards, check supplier information, review changes and keep every channel working from the same approved details.