Petiwoo
A storefront designed around pet care.
Species-aware product discovery and reliable commerce operations for a specialized pet-care storefront.
A pet catalog must reflect species and real stock.
Pet buyers browse by animal, category and product suitability. Storefront navigation must also show relevant prices and availability instead of treating every product as the same generic listing.
- Species and category-driven discovery
- Availability matters before checkout
Catalog APIs connect product pages to the cart.
The Next.js storefront provides search, product details, categories, basket and checkout routes. Commerce APIs supply catalog data, while Zustand manages local basket state and quantity calculations.
- Product and brand data come from APIs
- Cart quantities and totals are computed in state
Checkout code is not evidence of completed sales.
Source files confirm catalog pages, cart state and order-request pathways. Real payment processing, fulfilled orders and sales performance must be tested against deployed services, not inferred from a route.
- Evidence: Core-Petshop-Store and platform contracts
- No fabricated revenue, customers or conversion rates
Behind the decisions.
Explore the implementation context, technical trade-offs and evidence behind the three-part story. Open any chapter to read the full explanation.
0101 / CONTEXTSpecialist commerce needs specialist navigation.
Petiwoo is a pet retail experience in the GARTAL product family. The public store focuses on the relationship between the customer, the animal they care for and the products available to purchase.
The checked-in storefront is a Next.js TypeScript application with category navigation, product listings, product detail pages, basket and checkout pathways.
Its vertical identity makes product discoverability and accurate inventory information central parts of the interface.
- Pet-focused storefront
- Next.js / TypeScript
- GARTAL product family
0202 / THE PROBLEMA catalogue should understand the shopper.
A generic product grid ignores the differences between shopping for dogs, cats and birds. Visitors need intuitive species navigation, clear category context and a way to find the right product before comparing price or stock.
Retail operations also need to account for discounts, availability, stock state and changing product information. A pretty image cannot replace those responsibilities.
The product challenge is to connect specialist discovery with familiar and dependable ecommerce behavior.
- Species-aware wayfinding
- Search and categories
- Stock-aware product choices
0303 / STOREFRONTDiscovery is a product system.
The homepage source composes company profile, banners, product feeds, brands and a nested category tree. It maps catalogue data into a consistent home-product representation.
Categories can be filtered to second-level groups chosen for the homepage. Species normalization supports the navigation concepts of dogs, cats and birds.
When external data is missing, the source uses guarded fetch behavior rather than presenting hard-coded sales and inventory numbers as live facts.
- Category hierarchy
- Species normalization
- Live catalogue boundaries
0404 / COMMERCE FLOWSFrom browsing to a completed basket.
The repository describes product search, product details, cart state and checkout flow. Its TypeScript components are organized around browsing and purchase tasks.
The home route processes discount fields, sale prices, product attributes and stock context so the interface can distinguish a product promotion from normal catalogue presentation.
Zustand-backed basket state and commerce API integrations keep the storefront experience connected to transactional application logic.
- Product details and variants
- Cart and checkout
- Price and availability context
0505 / PLATFORM RELATIONSHIPA vertical product on shared foundations.
Petiwoo is identified by GARTAL documentation as an early product family with active pet retail and veterinary industry packs.
Retail and veterinary workflows need different domain models. The platform approach allows them to share contracts where appropriate while maintaining the distinction between shopping, appointments and care records.
This case study focuses on publicly documented storefront capabilities. It does not present veterinary records as if they were ecommerce products.
- Retail industry pack
- Veterinary pack boundary
- Shared cross-product contracts
0606 / CURRENT STATEThe product is real. The metrics must be too.
The code establishes a real storefront structure, catalog feeds and purchase routes. Its existence is not proof of conversion rate, revenue, order volume or a deployed public launch.
Instead of stock dog photographs or a fake sales dashboard, this portfolio now explains the actual information architecture, catalogue transformations and product decisions.
Future documented outcomes can be added when performance data and permissioned real captures are available.
- Repository-backed workflow
- No invented sales figures
- Documented next evidence
What is actually verified.
Repository source confirms storefront pages, product transformation, categories, brand feeds, inventory context and cart/checkout pathways. Illustrative sales figures or fabricated pet product records are deliberately excluded.
The overview explains documented implementation decisions. Production results and customer outcomes require separate verification.