Miwoo Kids
A WordPress and WooCommerce storefront for a Philippines-based children's apparel brand, with a 33-product catalog and per-item color and size variants.
Business
Children's apparel retailer, Philippines
Built
WooCommerce storefront with a 33-product, variant-heavy catalog
Stack
WordPress, WooCommerce, Elementor
Engineering focus
Commerce reliability, editor-friendly CMS, responsive design
Why this project matters
Why this project matters
Every product on this site carries up to 8 color options and 5 sizes — real combinatorial complexity, not a simple catalog. It's a useful example of whether a WooCommerce build holds up once variant handling, not just page design, is the hard part.
Who this is for
Who they are
Miwoo Kids PH is a Philippines-based children's apparel brand. The site's own footer describes it as "the home of premium cotton comfort for the little ones in your life."
What they do
They sell cotton clothing sets for children — tops, pajama sets and dresses — organized into Boys and Girls collections, priced in Philippine Pesos.
Who they serve
Parents shopping for children's everyday and sleepwear in the Philippines, plus wholesale buyers purchasing in bulk through a dedicated Wholesale entry point.
What the live site required
Not a wishlist from a kickoff call — what the delivered site visibly had to solve. Every requirement here is paired with the evidence that makes it true today.
Variant selection on every product, without a custom-built product configurator
CommerceEach product page exposes a color dropdown (8 options observed on one product) and a size dropdown (80–120 cm, 5 sizes), handled through WooCommerce's native variable-product system.
A catalog structure that scales past a handful of products
CommerceThe shop page paginates 33 products across 3 pages with sort options (popularity, rating, latest, price) — standard WooCommerce catalog behavior applied to a real, growing SKU count.
A distinct path for bulk buyers, separate from retail shoppers
UX"Wholesale" is a top-level navigation item, separate from the Boys/Girls retail categories.
A mobile-usable shopping experience
TechnicalAt a 390px viewport the site collapses to a hamburger menu and a 2-column product grid; at 834px (tablet) it shows a 3-column grid with a persistent search bar — three deliberately different layouts, not one design stretched across sizes.
Content and catalog changes the client's own team can make
ContentThe site runs on WordPress/WooCommerce — editor-managed platforms — rather than a static or custom-coded catalog.
Why this stack, not just what stack
Every technology on this project was a specific answer to a specific problem — never a default.
- 01
WordPress
Chosen because the client's team needed to manage products, pricing and content themselves without depending on a developer for every catalog change.
- 02
WooCommerce
Chosen because the store needed mature, tested cart, checkout and variant-selection behavior — color and size options per product — without building commerce logic from scratch.
Trade-off — WooCommerce's variable-product system handles fixed color/size combinations well, but it isn't a true configurator — a product requiring dynamic, rule-based combinations (rather than a pre-set list of variants) would need custom development on top of it.
- 03
Elementor
Chosen for the non-catalog page layouts (navigation, homepage sections, the Wholesale page) so they stay visually editable after handoff, without touching template code.
What the site can actually do
Variant-based product pages
Color and size selection per product, with a linked size chart — removes back-and-forth size questions before checkout.
Sortable, paginated catalog
Sort by popularity, rating, latest or price, paginated across multiple pages — keeps a 33-product catalog browsable as it grows.
Category navigation
Boys, Girls, Wholesale and Coming Soon as top-level sections — shoppers reach the right catalog in one click.
Shopping cart
Standard WooCommerce cart with a running total shown in the header — always visible, never a surprise at checkout.
Wishlist
Heart-icon wishlist accessible from the header — lets a parent save items across visits instead of re-searching.
Customer accounts
Login/account access from the header — repeat buyers skip re-entering details every order.
Wholesale channel
A separate entry point for bulk buyers — keeps retail and wholesale inquiries from colliding in one flow.
Responsive breakpoints
Distinct desktop, tablet and mobile layouts — the catalog stays usable regardless of device.
What the finished build shows
Specific, verifiable patterns in how this project is put together — not a feature list, but how the pieces fit.
Category taxonomy doing double duty
Boys, Girls and Wholesale aren't just navigation labels — the same taxonomy drives catalog filtering, so a single structure serves both browsing and organization instead of two separate systems.
Size chart kept inline, not a separate page
The size chart is linked directly from the variant selector on the product page rather than routing to a standalone page — one fewer navigation step at the exact moment a shopper is deciding.
Fixed pagination over infinite scroll
The 33-product catalog is split across numbered pages rather than loading continuously — a smaller, more predictable payload per page view as the SKU count grows.
The live experience
Every screen, captured directly from the live site — desktop, tablet and mobile.
How this project's engineering applies to your business
This pattern applies well beyond children's apparel.
Any retailer selling configurable products — furniture with fabric or finish options, print-on-demand goods, cosmetics with shade variants — faces the same variant-handling problem this catalog solves.
Businesses with tiered offerings, like professional services or membership models, can reuse the same segmented-path pattern that separates retail shoppers from wholesale buyers here.
And any team that needs to update products or content themselves, without calling a developer for every change, benefits from the same editor-managed WordPress and WooCommerce foundation.
If you remember four things
Commerce-first architecture
Cart, wishlist, accounts and variant selection all run on WooCommerce's tested commerce layer instead of custom-built equivalents.
Editor-managed catalog
Product, pricing and content changes don't require a developer — the client's team runs the catalog day to day.
Deliberate responsive breakpoints
Desktop, tablet and mobile each get a distinct, purpose-built layout rather than one design stretched across sizes.
Segmented buyer paths
Retail (Boys/Girls) and wholesale buyers are routed differently from the top-level navigation down.
Related work
More projects like this one
Planning a WooCommerce platform?
Tell us about your project and current platform. You'll hear back from a senior engineer within one business day.