Not a DTC pivot. A product truth layer.
A Shopify-based website concept for turning Maruchan.com into the canonical catalog that shoppers, retailers, ad platforms, search engines and LLMs can all understand.
One operating layer. Five downstream surfaces.
The site is valuable because it turns product truth into reusable infrastructure, not because it sells ramen directly.
Salsify
Governed product content, approvals, UPCs, nutrition, ingredients, images and retailer-specific fields.
Shopify
Consumer-facing catalog, collections, PDPs, recipes, campaign pages, product feeds and global market structure.
Reviews
Bazaarvoice or PowerReviews style syndication, ratings, UGC rights and product-level social proof.
Novi / AEO
Answer engine visibility, prompt/category gaps, product-level schema and content recommendations.
Retailers
Amazon, Walmart, Target, Kroger, Instacart and store locator flows as the conversion endpoints.
The website should publish what Salsify governs.
This keeps compliance and product accuracy intact while giving Maruchan a better owned experience for consumers and AI systems.
Salsify owns approved product truth.
Product names, claims, ingredients, nutrition, UPCs, images, market availability and retail-specific copy.
Shopify renders the catalog.
Family pages, PDPs, recipes, reviews, FAQs, product feeds and retailer CTAs.
Reviews and UGC add consensus.
Ratings, review count, fan sentiment, creator usage and rights-cleared visual content.
Schemas and feeds make it portable.
Google, Meta, TikTok, Pinterest, answer engines, retail media and Amazon attribution landing pages.
How the new Maruchan.com could be organized.
This is the IA to visualize first: product catalog at the center, recipes and reviews around it, and retail link-outs as the conversion layer.
The MVP is not a homepage refresh. It is the minimum viable product system.
The first build should prove Maruchan can publish complete product truth, route purchase intent, support global markets and give Novi clean pages to measure.
What must ship first
This is the smallest version that actually changes Maruchan’s digital architecture. Anything less risks becoming another brochure site.
What can wait
The site can preserve future optionality without letting future commerce ambition slow the first release.
The first release needs eight real surfaces.
Each one has a clear job in the conversion architecture: orient, filter, prove, route, localize or feed answer engines.
Homepage
Brand world, product entry points, recipes, fan favorites and market selector.
Product family page
Ramen, bowls, Instant Lunch, Yakisoba, GOLD and new product families.
SKU PDP
The canonical page for a single product, with product facts and retailer CTAs.
Where to buy
ZIP search, retailer availability, marketplace links and product-specific routing.
Recipes
Discovery by meal occasion, flavor, product, creator and cooking method.
Global market selector
Country, language, product availability, retailer and compliance routing.
Fan favorites
Reviews, ratings, UGC, best sellers and consumer consensus signals.
Search
On-site search that understands product names, flavors, recipes and store intent.
The PDP is the core product intelligence unit.
If Maruchan only gets one thing right, it should be this. Every PDP needs to answer shopper questions, feed structured data, route to retailers and give Novi a clean object to monitor.
Chicken Flavor Ramen
The classic Maruchan pantry staple: savory chicken-flavored ramen noodles ready in minutes and easy to customize with eggs, vegetables, chili crisp or protein.
Above the fold
Product name, family, pack image, ratings, taste profile, prep time, market availability and retailer CTAs.
- Primary CTA: Find near me or Buy at retailer
- Secondary CTAs: Amazon, Walmart, Target, Instacart
- Variant selector: cup, pack, bowl, multipack, flavor family
Product facts
Everything currently trapped in product systems or PDFs needs to be crawlable text on the page.
- Ingredients, allergens, nutrition and prep instructions
- UPC / GTIN, pack size, case pack and product family
- Approved claims, image alt text and compliance notes
Discovery modules
The PDP should connect products to use cases, not just list specs.
- Recipes using this product
- Similar flavors and formats
- Fan hacks, reviews and UGC
Machine layer
The same page should emit clean source-code signals for Google, LLMs, Novi and retail media landing pages.
- Product, Nutrition, Review, FAQ and Breadcrumb schema
- Canonical URL and market-specific hreflang
- Feed-ready fields for paid and retail media
Do not make DTC checkout the default. Design the site to capture intent and hand it to retail.
Shopify can power the product system without turning Maruchan.com into a fulfillment business. Checkout should be an option, not the strategy.
Retailer-first conversion. DTC only for controlled tests.
This respects the category economics, the Toyo Suisan retail reality and Katelyn’s need for practical infrastructure.
Global cannot be an afterthought if product data differs by country.
The selector is not just translation. It controls product availability, nutrition, claims, retailers, recipes, compliance and canonical URLs by market.
Selector experience
The UX should be visible in the header and persistent enough that shoppers know which catalog they are browsing.
What the website team and Novi should align around.
This turns the concept into implementation language: the fields, modules and decisions that need to exist before design starts.
Product data model
Map Salsify fields into Shopify products, variants, metafields and metaobjects. Decide which fields are global, market-specific and retailer-specific.
PDP module inventory
Define required PDP modules: hero, product facts, nutrition, allergens, reviews, recipes, similar products, FAQ, schema and retailer CTAs.
Retail routing logic
Define when to show Amazon, Walmart, Target, Instacart, Kroger, store locator, unavailable states and market-specific retailer links.
Checkout policy
Decide whether Shopify checkout is fully disabled, hidden, passworded or reserved for bundles and drops. Do this before UX design.
Global rollout model
Choose market URL structure, language handling, compliance workflow, localized recipes and product availability rules.
Novi handoff
Ask Novi what exact crawl, schema, feed and content requirements they need to monitor AI answer visibility by SKU and category.
Shopify should be the catalog experience, not the product authority.
The site works best when each platform has a clear job and product data does not get manually duplicated across systems.
Salsify fields to sync into Shopify
Approved product content should flow into Shopify products, variants, metafields and metaobjects.
- Product title, family, flavor, format and pack size
- UPC / GTIN, ingredients, allergens and nutrition
- Approved claims, images, alt text and market availability
- Retail-specific URLs and pack configurations
- Compliance reviewed PDP copy and FAQs
Shopify fields to power the site
Shopify then turns those records into pages, feeds and campaign surfaces.
- Product family pages and SKU-level PDPs
- Recipe metaobjects connected back to products
- Retail link-out modules and campaign landing pages
- Google, Meta, TikTok and Pinterest catalog feeds
- JSON-LD schemas rendered into source code
Reviews and UGC layer
This should likely be Bazaarvoice or PowerReviews, not a manual scrape of retail reviews.
- Collect product-level ratings and reviews
- Show aggregate rating on owned PDPs
- Syndicate reviews to retail partners where permitted
- Manage UGC rights and moderation
- Create review schema and fan favorite surfaces
Novi / AEO optimization layer
Novi should be the visibility and recommendation layer, not the source of truth.
- Monitor answer engine visibility by product and category
- Identify missing PDP attributes or schema gaps
- Recommend prompt/category targets
- Prioritize PDP rewrites and FAQs
- Track which pages get cited over time
The source code should be as intentional as the page.
LLM-friendly content is not just visible copy. It is structured data, crawlable HTML, metadata, internal linking and product facts in predictable fields.
Required schemas
Visible content
Taste profile, preparation, ingredients, allergens, nutrition, reviews, related recipes and retailer availability.
Source code content
JSON-LD, canonical tags, metadata, product feed fields, image alt text and crawlable HTML.
Feed content
GTIN, product title, description, image, availability, retailer URLs and market fields for downstream platforms.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Maruchan Chicken Flavor Ramen",
"brand": { "@type": "Brand", "name": "Maruchan" },
"gtin": "From Salsify",
"category": "Instant ramen noodles",
"description": "Classic savory chicken flavored ramen ready in minutes.",
"nutrition": {
"@type": "NutritionInformation",
"servingSize": "1 package",
"calories": "From Salsify"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "2418"
},
"offers": {
"@type": "AggregateOffer",
"seller": ["Amazon", "Walmart", "Target", "Instacart"]
},
"subjectOf": [
{ "@type": "Recipe", "name": "Chicken ramen egg drop soup" },
{ "@type": "FAQPage", "name": "Chicken Flavor Ramen FAQ" }
]
}Build it in phases so the data model comes first.
The first release should prove the PDP and product data system before expanding into community, personalization and optional commerce.
Product intelligence foundation
Homepage, product index, family pages, SKU PDPs, where-to-buy, recipe graph, FAQ system, global market selector, search and schema layer.
- Salsify field mapping
- PDP schema system
- Retail link-out + checkout policy
Discovery and community layer
Fan favorites, UGC galleries, creator recipes, review syndication, flavor finder and new product launch hubs.
- Bazaarvoice or PowerReviews
- Recipe-to-product graph
- LLM FAQ expansion
Commerce optionality
Limited drops, pantry boxes, GOLD discovery kits, campaign landing pages and Amazon Subscribe & Save routing.
- No default DTC push
- Retailer conversion first
- Test only where economics work
Maruchan.com should become the product catalog LLMs trust.
Keep Salsify as the governed product source of truth, use Shopify as the global catalog and consumer experience layer, add a review and UGC syndication partner, use Novi as the AEO intelligence layer, and route purchase intent to retail partners. This gives Maruchan ecommerce-grade infrastructure without pretending ramen needs a full DTC checkout motion. The MVP should explicitly include SKU-level PDPs, a retailer-first conversion layer, a global market selector, localized product data rules and a clear policy for if or when Shopify checkout appears.