The cloth is woven from this chapter's 4 exhibits: each weft is one exhibit's own data, normalised; each warp group is a section. The probe reads the exhibit's own value where it crosses. Procedural visualisation, not a measurement.
EX 52
EX 53
EX 55
The chapter as a draft: 7 sections, 3 exhibit wefts, one shuttle.
Lead exhibit · 52Decision mapillustrativeA pilot should test the conditions that could overturn adoption
01 / 05
Read-out
Method and source
Illustrative GFT test-planning positions informed by the cited material and process sensitivities. Horizontal position is novelty relative to the locked workflow, where 0 is an unchanged repeat and 10 is entirely new. Vertical position is the consequence of releasing an unverified result, where 0 is negligible and 10 is severe. Coordinates are author-assigned for protocol design, not observed defect rates or probabilities.
Unit: illustrative planning positions from 0 to 10. Status: illustrative. Sources: S05, S15, S30. Illustrative figures are teaching examples, not measured factory results.
The chapter's warpBar: share of the reading · square: an exhibit
A controlled pilot should decide whether a defined apparel service deserves adoption, not demonstrate that a preferred machine was right all along. Its comparison must begin with the route that would otherwise deliver the same garment, preserve physical approval, include every learning and recovery cost, and test cases excluded from calibration. Thresholds and stop conditions belong in the protocol before results arrive. GFT therefore proposes a matched, held-out pilot whose valid outcomes include stop, outsource, repair and retest, or adoption of only the scope that passed. The method extends GFT's Cameroon textile programme as an evaluation design. It does not presume an existing GFT production line, local demand, supplier performance or measured savings.
¶ 01
13.13 min · 7 paragraphs · read with a related exhibit
A pilot needs an explicit counterfactual
The counterfactual is the service that would be used if the proposed digital route were not adopted. It may be conventional physical sampling followed by an outsourced print run, decoration of stocked blanks through an existing supplier, or another route that can genuinely fulfil the intended order. It is not a deliberately weak assembly of unnecessary steps. The comparison should name the garment, approval obligations, accepted quantity, delivery region and commercial terms that both routes must satisfy. Only then can a difference in time, cost or resource use inform adoption.
Equivalence starts with function rather than appearance. The historical VTT printing study makes batch size, quality, durability and product lifetime important to its comparison, rather than treating printed area as a sufficient description of the service.[S26] A pilot should apply the same discipline to a garment. A digital sample that avoids a physical fitting but leaves fit unresolved is not equivalent to an approved physical sample. A printed article with inferior care performance is not equivalent to one that meets the buyer's agreed use conditions. The protocol must either close those differences through testing or retain them as explicit limitations.
Residual physical work therefore belongs in both route definitions. Research comparing virtual and physical fitting concludes that simulation cannot fully replace a real physical fitting because technical issues remain.[S07] The proposed digital route might still reduce some iterations, but the pilot must count the fitting, strike-off, care test or sewn approval that remains necessary. It should not compare a complete baseline service with an incomplete digital preview. The unit of comparison is an approved style or retained order, with all work required to reach that state.
A useful design pairs routes at the style or order level. The same technical brief, material requirement, size coverage, artwork and acceptance evidence go to the baseline and proposed workflows where practical. Pairing reduces the chance that an easy style flatters one route while a difficult style burdens the other. It also lets the reviewer inspect differences within each pair instead of relying only on cohort averages. When simultaneous execution is impossible, the record should identify changes in staff, supplier, material lot and buyer requirements between periods.
¶ 04
Some factors cannot be held constant without distorting the decision. A digital route may require fabric digitisation that the baseline does not need. An outsourced baseline may include courier movement that an internal route avoids. Those differences are part of the routes and should remain visible. The analyst should not force identical activity lists. The requirement is an equivalent delivered outcome, not identical work. Each route receives the activities and costs that it actually needs to reach that outcome.
¶ 05
Note
The baseline also needs an availability statement. If no stable internal sampling route exists, the protocol should compare documented supplier offers and observed outsourced work rather than inventing current factory performance. If a reliable baseline cannot yet be measured, the first pilot stage is baseline reconstruction. That work may delay an equipment decision, but it prevents a false saving from becoming the foundation of one.
¶ 06
13.23 min · 8 paragraphs · 1 exhibit
The test matrix must cover the intended difficulty
Related · chapter 108 paragraphs step it
Related exhibit 43 · chapter 10Decision mapillustrativeA metric is useful only when its denominator is stable
01 / 05
Read-out
Method and source
Illustrative GFT scoring. On each axis, 0 means absent or unstable and 3 means explicitly defined or directly connected to the retained-order decision. Positions are proposed architecture judgements, not measured performance or universal rankings. Scores should be revisited when definitions or service boundaries change.
Unit: illustrative design score, 0 to 3 on each axis. Status: illustrative. Sources: S03, S28. Illustrative figures are teaching examples, not measured factory results.
A pilot built only from easy repeats cannot support a broad service claim. The test matrix should represent the conditions under which the proposed offer would actually operate: material and blank variation, light and dark bases, print placement, construction complexity, size coverage, new artwork and exact repeats. Each dimension needs a reason tied to a failure mechanism. The objective is not maximum variety. It is enough deliberate variation to expose the conditions that could overturn adoption.
Material direction belongs in that design because mechanical behaviour can affect virtual fit. A study of virtual garment fit found that tensile properties in the weft direction had the greatest influence for the diagonal-cut garments it examined.[S05] That study does not supply a general ranking for every garment. It shows why a pilot containing only one stable material and one grain orientation could miss a consequential sensitivity. Bias-cut or highly deformable cases should be included only if they fall inside the intended service, and their results should remain separate from simpler constructions.
Print preparation creates another axis. Manufacturer guidance for one garment-printing workflow states that pretreatment is necessary when white ink is used or when printing onto polyester.[S30] The statement is specific to that workflow, not a universal rule. It nevertheless shows why light and dark bases, fibre content and ink configuration cannot be treated as interchangeable presentation options. The matrix should record the actual preparation, white-ink use, curing route and material identity for every case.
Physical handling must also survive the comparison. A garment-printing guide identifies heat curing as the final stage of its described direct-to-garment process, while film transfer uses a different sequence.[S15] A test that times only digital design or printer deposition would omit work that can affect accepted output. Placement complexity should therefore include the subsequent curing, cutting where relevant, assembly and inspection needed by the chosen route. An engineered placement across panels poses a different test from a small chest image, and the two should not share an unqualified average.
Repeat work needs its own stratum. An exact repeat tests whether a locked package can be reproduced. Revised artwork tests controlled prepress and approval. A new style tests pattern, material and development capability. Combining them into one productivity measure hides where learning transfers. The matrix should label the novelty of every case before execution so that a favourable concentration of repeats cannot be discovered after the fact and presented as representative of all work.
Exhibit 52 illustrates how the team can prioritise conditions for coverage. The coordinates are judgement-based planning positions, not defect probabilities or measured performance. Their purpose is to make omissions visible before cases are selected. A high-consequence, novel condition should not disappear merely because it is inconvenient to test.
Sample counts should follow observed variability and the precision needed for the decision. A stable exact-repeat family may need fewer observations than a family whose results vary by material lot or fit participant. The protocol should begin with a baseline variability assessment, identify the consequential measures and state what difference would change the decision. It should then document why the planned coverage is informative. There is no defensible universal pilot quota that applies to every garment family.
Small coverage can still produce useful learning, but its conclusion must remain narrow. If only one material lot or size cluster is tested, adoption applies only to that bounded condition pending further evidence. If an important cell cannot be filled, the matrix should show it as untested rather than allowing the completed cells to imply coverage. The final decision inherits the structure of the test, including its empty cells.
13.32 min · 7 paragraphs · 1 exhibit
Calibration work must not consume the whole test set
Step 1 of 7Allocate development cases
Exhibit 53 · illustrativeCalibration and validation must remain separate
Allocate development cases
Allocate development cases. From Run paired physical checks (Revision becomes new candidate). Leads to Calibrate and correct. · illustrative
Calibration and validation answer different questions.
Calibrate and correct
Calibrate and correct. From Allocate development cases. Leads to Lock workflow and gates. · illustrative
Lock workflow and gates
Lock workflow and gates. From Calibrate and correct. Leads to Open held-out cases. · illustrative
Open held-out cases
Open held-out cases. From Lock workflow and gates. Leads to Run paired physical checks. · illustrative
Run paired physical checks
Run paired physical checks. From Open held-out cases. Leads to Reconcile all outcomes, Allocate development cases (Revision becomes new candidate). · illustrative
Reconcile all outcomes
Reconcile all outcomes. From Run paired physical checks. Leads to Apply decision rule. · illustrative
Apply decision rule
Apply decision rule. From Reconcile all outcomes. End point. · illustrative
The method behind it: GFT note.
Method and source · Exhibit 53
Illustrative protocol design. Development cases inform calibration; validation cases remain untouched until the workflow and criteria are locked. A change after validation begins creates a new candidate. No software performance, sample size or achieved approval rate is asserted.
Unit: illustrative GFT evaluation sequence. Status: illustrative. Sources: S04, S06, S07. Illustrative figures are teaching examples, not measured factory results.
13.3 · the bodyExhibit 53 above; its figures are illustrative where marked.
Calibration and validation answer different questions. Calibration adjusts the workflow until it can represent the intended material and garment. Validation asks whether the locked workflow succeeds on cases that did not shape those adjustments. If every style is available for tuning, the final result measures how well the team fitted its tools to the test set. It does not establish transfer to the next order.
The separation applies to more than a fabric model. Development cases can be used to select avatars, resolve pattern imports, choose print settings, revise preparation, establish curing work and train reviewers. Validation cases must arrive after those choices are frozen. The locked package should identify software and process versions, material assets, pattern rules, simulation settings, artwork handling, physical test methods and decision criteria. A shared folder name is not an adequate lock; the record needs a reproducible revision identifier.
¶ 02
Simulation controls make the reason concrete. The physical-versus-virtual drape study includes a phase examining the effect of particle distances on virtualised fabric.[S04] Resolution can therefore be part of the experimental condition, not an incidental preference. During validation, the team should not change particle distance, collision handling or related settings until a difficult case looks acceptable. Such a change creates a revised candidate and returns that case to development.
Physical comparison remains the check on the calibrated digital decision. The virtual-fit research supports a real fitting gate, while the real-versus-virtual garment study compares distance ease at named bust and waist cross-sections.[S07][S06] A pilot should define its own corresponding physical and digital observations before seeing the results. Locations, poses, material state and measurement methods must match as closely as possible. Differences should be reported at their locations rather than averaged into a reassuring overall fit score.
Exhibit 53 sets out the proposed evidence sequence. The return edge is important: a material or workflow correction does not merely add a note to a failed validation. It creates a new candidate that needs held-out evidence appropriate to the change.
The held-out set need not be secret or theatrically concealed. Its integrity comes from not using it to make workflow choices. Buyers and operators can know which cases are included, while the technical team commits to the evaluation settings in advance. Where buyer approval requires a revision, the ledger should show that the evaluation became developmental and identify what new validation is required.
¶ 06
13.42 min · 8 paragraphs · 1 exhibit
Acceptance thresholds belong before the results
A gate written after the results tends to fit the preferred answer. Before execution, the buyer and operations leads should agree what must pass, which evidence is acceptable, who decides and what happens after failure. Thresholds should reflect the garment's intended use, the buyer's specification, process capability and the decision's consequence. A supplier demonstration or an unrelated publication cannot supply a universal acceptance limit.
Physical tests need complete protocols rather than method names alone. ISO's laundering scope warns that industrial and hospital articles may require special procedures that are more severe in some aspects.[S10] Its rubbing scope distinguishes dry and wet rubbing cloths.[S11] Its domestic washing and drying scope states that a complete test consists of both washing and drying.[S12] These public catalogue entries help define the questions; they do not provide the pilot's pass grades. A qualified laboratory or competent reviewer must agree the full procedure, specimens, conditions and evaluation before testing.
Fit gates require the same specificity. The small real-versus-virtual garment study provides a warning against transferring study-specific discrepancies into a new operation.[S06] The pilot should instead state the locations, poses, intended wearer coverage, measurement uncertainty and buyer-approved tolerances that matter for this garment. It should record both evaluator observations and relevant wearer feedback. A mean difference cannot compensate for a local failure that prevents use.
Operational gates should cover the original delivery promise, complete retained-order contribution and recovery work. Delivery is measured against the promise made when the order was accepted, with later amendments shown separately. Contribution includes failed work, refunds and remakes rather than only clean output. Recovery includes reprints, repeated tests, additional courier movements and the labour required to correct them. A favourable development result cannot compensate for a service that loses money or arrives late under the agreed criteria.
¶ 04
Exhibit 54 provides the gate sheet's minimum structure. Its cells deliberately do not invent numerical thresholds. Each organisation must complete them from its own buyer, process and risk requirements before running the pilot.
Exhibit 54RegisterillustrativeEvery acceptance decision needs its evidence and owner
Gate
Fit and construction
Required evidence and threshold origin
Paired observations at agreed locations and poses; buyer-approved tolerances
Accountable role
Technical and quality leads
Failure consequence
Hold affected style or size
01 / 07
Read-out
Open the full register (7 rows)
Fit and construction
Paired observations at agreed locations and poses; buyer-approved tolerances
Technical and quality leads
Hold affected style or size
Colour and care
Agreed laundering, drying and rubbing protocols; buyer criteria
Quality lead and laboratory
Hold affected material route
Delivery
Original promise, dispatch and buyer acceptance records
Fulfilment lead
Review promise or stop route
Retained contribution
Complete order ledger after the defined return window
Commercial and operations leads
Reject or redesign economics
Resource boundary
Metered or allocated inputs with accepted and retained denominators
Operations and analysis leads
Narrow the supported claim
Recovery and hours
All reprints, remakes, courier work and paid correction hours
Production and people leads
Correct planning before retest
Evidence integrity
Complete identifiers, attempts, revisions and source records
Protocol custodian
Block adoption decision
Method and source
Illustrative GFT protocol structure. Thresholds, methods, editions, observation windows and named accountable persons must be completed before execution. Public standards scopes do not supply buyer pass grades. No measured pilot result is shown.
Risk assessment should determine which failure can be conditional and which must stop the route. IFC guidance supports using a risk assessment form to prioritise which risks should be addressed first.[S18] Prioritisation does not mean averaging a severe safety or physical failure against commercial success. The gate sheet should identify non-compensable failures explicitly. A lower-priority documentation gap may receive a bounded correction period; an unclosed physical release failure keeps the affected service out of adoption.
Working conditions belong inside the protocol rather than in a later social review. OECD guidance identifies inefficient production planning and poor purchasing practices among common factors associated with excessive working hours.[S28] The pilot should therefore predefine how it records work outside normal shifts, late buyer changes and urgent recovery. Meeting a delivery gate through unrecorded or unacceptable hours is not a pass. Applicable employment obligations require qualified local review rather than inference from international guidance.
Finally, the decision rule should handle missing evidence. An unmeasured gate is not a passed gate, and an incomplete return window is not evidence of retention. The review can postpone a decision, narrow the claim or commission another test. It should not convert absent data into a favourable assumption. This rule protects the pilot from ending with a precise score whose most important fields were never observed.
¶ 03
Interlude · the cloth half-woven
4 exhibits carry this chapter's argument.
Woven: sections 13.0 to 13.4Still to weave: 13.5 to 13.7
13.53 min · 7 paragraphs · read with a related exhibit
The ledger must include failures and learning costs
Related · chapter 027 paragraphs step it
Related exhibit 08 · chapter 02Material flowillustrativeOrders can disappear before they become retained sales
01 / 06
Read-out
Method and source
Illustrative GFT cohort accounting template informed by S03, S20 and S0203. Uses a symbolic base of 100 enquiries to demonstrate flow conservation across commercial and fulfilment leakage points. Values are illustrative accounting placeholders, not observed Cameroon conversion rates; actual counts must be populated from the pilot order ledger.
Unit: illustrative index cohort (100 enquiries). Status: illustrative. Sources: S03, S20, S0203. Illustrative figures are teaching examples, not measured factory results.
A pilot ledger should explain where every hour, material unit and order outcome went. Recording only successful samples would remove precisely the work that determines whether adoption is worthwhile. Each style or order needs a continuous record of attempts, revisions, rejected prints, physical tests, courier movements, approvals, production recovery and final acceptance. The denominator is the full cohort entered into the test, including withdrawals and failures, with reasons attached.
Learning costs need a visible home. Fabric digitisation, pattern conversion, staff training, trial prints, software setup and protocol development may be treated as cohort or period costs rather than assigned arbitrarily to one garment. The ledger should show the chosen allocation and the unallocated period total. It should also distinguish a one-time investigation from a recurring obligation. That distinction aids interpretation, but it must not be used to make inconvenient initial work disappear from the adoption comparison.
The same rule applies to work outside the expected route. A supervisor correcting a file at night, a second supplier visit, a replacement blank and an urgent delivery all belong to the case that caused them. OECD guidance on planning and purchasing risks makes these events relevant to responsible operation as well as cost.[S28] Paid hours should reconcile to work records, while waiting time should be distinguished from active labour. An idle printer and an idle worker are different states and should not share one vague downtime field.
Commercial closure comes after the defined cancellation, refund and return window. Net retained sales must reflect the outcome after that window, while the cost ledger retains everything consumed by cancelled and refunded work. Remakes and replacements belong to the original order, not to new demand. The pilot should reconcile ordered, started, accepted, dispatched, returned, refunded and retained states so that an internally successful print cannot become a successful sale without buyer evidence.
The source records must reconcile to the paper's sampling-cost and unit-economics dictionaries before the review. Development hours, physical iterations, residual samples and courier costs feed the sampling comparison. Materials, direct production labour, energy, delivery, recovery and net retained sales feed order contribution. Shared period costs remain visible in both models without being counted twice in a combined conclusion. A reviewer should be able to move from every summary value to the underlying events.
The example is useful because it denies the analyst a simple equipment narrative. Fewer physical samples can coexist with higher total cost once digital labour, calibration and period capability are counted. Conversely, a digital route should not be rejected merely because it carries those costs if measured outcomes show sufficient avoided work. The correct response is to observe the actual residual requirement and labour distribution, then test whether the decision remains stable across defensible conditions.
13.62 min · 7 paragraphs · 1 exhibit
Uncertainty belongs in the decision
A pilot average can hide the cases that determine adoption. The review should retain pair-level differences, cohort totals and results by material, novelty, size coverage and placement complexity. For each matched pair, the arithmetic difference can be calculated as proposed route minus baseline for development hours, complete cost and other common measures. The sign and unit must remain consistent. A favourable mean accompanied by repeated failures in one intended service cell is not evidence for the whole offer.
Variation should be shown before any summary interval is attempted. A small pilot can reveal the range observed within its cases, but that observed range is not a confidence interval and does not bound every future order. Statistical intervals require a defensible sampling and analysis method. Where those conditions are absent, the report should use descriptive results and explicit scenarios instead. More decimal places cannot compensate for a weak sampling frame.
¶ 02
Exhibit 55 extends the worked example by varying both digital labour and residual physical samples. The bars are scenario bounds, not confidence limits or observed outcomes. They show how an apparently close decision can change under assumptions that the pilot needs to measure.
Exhibit 55Review bandsillustrativeThe pilot must expose uncertainty as well as average performance
01 / 03
Read-out
Method and source
Illustrative scenario arithmetic, not observations or statistical intervals. For each residual-sample case, fixed non-labour cost is 180,000 calibration + 420,000 software and training + residual samples x 45,000. Low and high digital labour bounds are 12 and 16 hours per style x 12 styles x 4,000 XAF; mid uses 14 hours. Baseline comparison and all assumptions appear in the worked example. No local prices, sample rates or forecast are asserted.
Unit: illustrative XAF per 12-style cohort. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.
The scenario bounds expose two different evidence needs. Residual-sample count is a physical approval outcome that the pilot can observe by style and cause. Development hours require disciplined time capture across pattern, digitisation, simulation, review and correction. If either field is missing, the analyst should not select whichever scenario makes the route attractive. The appropriate conclusion is that the economic gate remains unresolved.
¶ 01
Study-specific discrepancies also need careful handling. The real-versus-virtual garment study compares named cross-sections, but its observations belong to its tested garments and method.[S06] They should motivate paired measurement, not become acceptance tolerances or expected error rates for a new service. Likewise, the on-demand wool-knitting LCA uses environmental measurement and denominator choices for a different product system.[S25] It supports stating boundaries carefully, not transferring its results to printed cotton apparel in Cameroon.
Sensitivity analysis should change one consequential assumption at a time and then examine combinations where dependencies matter. Labour and residual samples may be related: additional digital correction could reduce physical iterations, or could create more of them. The model should not assume a convenient independence if the case records suggest otherwise. Correlation in a handful of cases is still not a proven causal relationship, but it is a reason to inspect mechanism and collect better paired evidence.
¶ 03
Decision uncertainty can justify three bounded responses. More observation is appropriate when the route passes its non-compensable gates but the economic or operational result remains unstable. Narrowing is appropriate when only some cells pass consistently. Stopping is appropriate when the route fails a required physical condition or cannot produce a viable result across reasonable conditions. Uncertainty is not always a reason for another pilot; it can also reveal that the proposed scope was too broad.
¶ 04
13.72 min · 7 paragraphs · read with a related exhibit
Scale only the service that passed
The final review should choose among stop, repair and retest, outsource, or adoption of a precisely bounded service. Expansion is not the default reward for completing the protocol. Stop is appropriate when the route cannot meet a required condition or its disadvantage is clear. Repair and retest require a named cause and a credible correction. Outsourcing remains a valid service design when an external route provides the better accepted outcome. Adoption applies only to the material, garment, approval and order conditions supported by the evidence.
A pilot review packet should contain the counterfactual sheet, test matrix, locked workflow, held-out register, gate sheet, complete, reconciled cohort ledger, pair-level results, scenarios and deviations from protocol. It should identify which planned cases were not run and which records remain incomplete. Failed cases stay in the evidence register with their original identifiers. Removing them would turn a service evaluation into a marketing selection and would prevent the next reviewer from understanding what was actually learned.
¶ 02
Corrective action should follow risk and cause rather than enthusiasm. IFC guidance supports prioritised risk treatment inside an operating management system.[S18] OECD's more recent garment due-diligence guidance expects each company to identify its priority risks from its individual circumstances, including risks not listed in the guidance.[S29] The pilot owner should therefore record the affected condition, corrective action, accountable role, evidence needed and retest scope. An open safety or physical release failure prevents the affected route from advancing regardless of its commercial score.
The reviewer should also be independent enough to reject the equipment story. A person who approved the purchase can contribute operational evidence, but the gate decision needs a reviewer authorised to accept a negative result. Supplier demonstrations and vendor calculations may inform the protocol, yet they cannot determine its thresholds or replace local observations. This governance condition matters most when the pilot appears close to passing and the organisation has already publicly committed to adoption.
¶ 04
Scope control is the last defence against overgeneralisation. A pass for an exact-repeat, single-material service does not establish custom fit, a new fabric family or automatic production release. A change to material, artwork complexity, size coverage, supplier, care requirement or delivery promise should trigger a documented carry-over decision. Some evidence may remain relevant, but the changed condition needs the tests its new failure modes require.
¶ 05
Note
GFT's practical recommendation is to approve the smallest validated scope, retain the baseline where it performs better, and treat a rejected route as useful evidence rather than wasted work. The pilot has succeeded when it produces a defensible decision with its failures and uncertainty intact.
¶ 06
Check the record
The chapter keeps its sources within reach.
Every knot is a source this chapter cites; select one to read its record, or filter the register by grade. Publication dates and inherited-source limits stay explicit. Read the paper's full evidence summary.
14 sources · 33 citation marks on this pageMost cited: S06, 4 times
Grade AGrade BGrade CKnot size: citations on this page
All 14 records shown
c13-S04 · Grade B
Dongguk University research portal; Taylor & Francis, Journal of the Textile Institute
Comparative study of physical and virtual fabric parameters: physical versus virtual drape test using commercial 3D garment software
The last phase investigates the effect of particle distances on virtualized fabric.
2025. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
S28Organisation for Economic Co-operation and Development. 2018.
S25TU Delft Research Portal; author abstract of Textiles article. 2026.
S29Organisation for Economic Co-operation and Development. 2026-02-26.
Keep the thread · chapter 13 of 14
Chapter 14 picks up the thread.
Move the shuttle along the rack to preview any chapter: its sections, exhibits and reading time. Draft web edition. This research is not investment, legal or tax advice; illustrative models are not measured factory results.
The paper's rack · 14 boltsBolt length: reading time
1.1
1.2
1.3
1.4
1.5
1.6
1.7
01Part I: Confirm the order before choosing the machine
Local value starts with a garment that can be reordered
GFT argues for a measured order-to-garment service that reduces speculative commitments while retaining physical proof of quality.
1.1Cameroon needs processing capability that wins repeat orders
1.2Printing, sampling and order timing solve different problems
1.3A digital sample must lead to a manufacturable specification