Inside PerfittSize: Three Steps from PDP to Model-Specific Size Guidance

Footwear ecommerce teams often hear the phrase “personalized size recommendation” without seeing what the shopper actually experiences on a product page.

PerfittSize is easier to evaluate when the journey is broken into three concrete moments: the product-detail-page entry point, the shopper context that informs the decision, and the recommendation for the exact footwear model being considered.

This walkthrough uses current images from Perfitt’s public product demo, cross-checked against Perfitt’s approved 2026 product materials. Individual client implementations can vary by market, catalog coverage, interface configuration, and available measurement or profile options.

Step 1: Give the shopper a product-level entry point

The first job is to make fit guidance available where the decision happens: on the product detail page.

In the public Perfitt demo, a shopper can open the measurement and recommendation flow from a module embedded in the product page. Depending on the implementation, PerfittSize can also show a product-level size tendency indicator before the shopper begins a personalized flow.

The purpose of this entry point is practical. A generic size selector asks the shopper to interpret the product alone. A fit-guidance entry point gives the retailer a place to connect product data with information about the shopper.

For an ecommerce team, the implementation questions include where the entry point appears, which product records are covered, how unavailable sizes are handled, and what language the shopper sees before sharing profile or measurement data.

Step 2: Build enough shopper context for a useful recommendation

A model-specific recommendation needs more context than a regional size label.

Perfitt’s public demo shows a smartphone flow that guides the shopper through photographing the top of each foot. Perfitt’s product materials also document profile inputs and measurement options that can support the recommendation. The exact path is configured for the client and market; a smartphone scan should not be described as mandatory for every implementation or every returning shopper.

This is the point where the experience moves from “What size do people usually buy?” toward “What do we know about this shopper’s foot and fit context?”

For buyer and implementation teams, the important checks are explicit consent, privacy language, the profile fields used, measurement availability by device and market, and what happens when a shopper skips or cannot complete a measurement step.

Step 3: Return guidance for the footwear model on the page

The output is not a universal shoe size. It is guidance for the product the shopper is viewing.

The current public demo shows a recommended size inside the product page and a state in which recommendations can differ across product configurations. Perfitt’s approved product materials describe matching customer context with the shoe’s model-level inner-dimension and fit data, then returning ranked size options where applicable.

That distinction matters. A size chart translates labels. A recommendation layer evaluates a relationship between a shopper and a specific product record.

Perfitt has previously shown that shoes carrying the same nominal size can have different measured internal dimensions. That measurement story explains why product-level data matters. This walkthrough shows where that data becomes visible to the shopper: inside the purchase journey for a specific model.

What an ecommerce team should validate before launch

• Product mapping: confirm that each PDP and variant resolves to the correct model and size records.

• Coverage: define which products can receive guidance and how uncovered products are presented.

• Shopper path: decide which profile, prior-size, or measurement options are available in each market.

• Recommendation language: explain what the output means without presenting it as a guarantee.

• Edge states: test missing data, unavailable recommended sizes, returning shoppers, and measurement interruptions.

• Privacy and consent: review the data flow and customer-facing disclosures for the deployment.

• Measurement plan: define how the team will evaluate recommendation engagement, retained purchases, exchanges, and returns without confusing correlation with causation.

The buyer-level takeaway

PerfittSize is not simply another size label on the PDP. The product experience connects three layers: the product the shopper is viewing, the shopper context available for the decision, and model-specific fit guidance returned at the point of purchase.

The value of a walkthrough is that it makes the implementation discussable. Ecommerce, product, legal, analytics, and operations teams can see the exact customer moments they need to validate instead of evaluating an abstract “AI sizing” claim.

Product note: Screens shown here come from Perfitt’s public demo as verified on October 28, 2026. Client interfaces, enabled inputs, catalog coverage, and recommendation states can vary by deployment.

Sources: Perfitt public product demo; PerfittSize product features.