About this block

Pattern Remake File makes the case that a custom build is expensive once. Three promise rows explain that the file holds every measurement forever, that a remake skips the pattern day and prototype so the wait drops from eight weeks to about three, and that it prices at 1.1x. A static pattern record card sits beside them with real measurements and the file number.

Data is a promises array and a record array, one mapped into a checked list, the other into a definition list on the card. The footer that spells out the remake price today against the original build price is the moment the 1.1x claim becomes concrete for the buyer.

When to use

Reach for this block after the custom pricing table so the remake math lands once the base custom prices are set. The record card numbers and the two build prices in the footer must be internally consistent to stay honest.

A natural flow around it on an Ecommerce Pro page:

Before

• Custom pricing table

After

• Custom order intake
• Custom orders FAQ

What you can display

One strong use is the remake promise beside a real pattern record. Other record card configurations:

• Repair record. The service history of one bag, each visit dated with the work done.
• Fit record. A made to measure file, the body measurements the pattern was cut to.
• Reorder record. A fleet client’s standing spec, the run count and last order date shown.

Tip: "the second bag never pays for the first bag's homework" frames the file as a saving, not a lock in, which is what makes the remake feel worth keeping.