A small, well-scoped project: the ACT Printing ordering flow
Netbase upgraded the existing online store of ACT Printing, a custom apparel and print shop, with a guided, mobile-first ordering flow, built and tested on staging over about 20 to 25 working days. No business result is published. This record is here because it shows the size of a sensible first project, which most suppliers never put on a website.
Submit a project See all work records
Record at a glance
- Evidence level
- Portfolio record: delivered scope, no result published
- Client
- ACT Printing, a custom apparel and print shop; no region and no domain are published
- Service
- Custom Product Engineering
- Delivered scope
- A guided mobile-first ordering flow across three to four priority product groups
- Duration
- About 20 to 25 working days, then a handover walkthrough and a 30-day bug-fix window
- Published results
- None
What the shop needed
A shop that prints on garments must collect more than a size and a quantity: where the print goes, which artwork belongs in each place, which colours are wanted, and how many of each size. Collected badly, that arrives as an order somebody has to telephone back about. The shop already had a store; it needed the ordering step on its main products to stop losing information.
What was built
Across three to four priority product groups:
- print-location zones for the front, back and sleeves, with artwork uploaded and previewed against its own location;
- garment colour selection, including orders that mix more than one colour;
- a grouped size-package builder with a live total;
- quantity-tier pricing on the shop's own products, a term of the shop's store and never a Netbase rate;
- contextual upsells at the point where they make sense;
- structured order data, with a production summary per order for staff.
It was built and tested on staging, with client acceptance testing before release.
The scope boundary, which is the point of this record
The delivered scope is the phase one agreement and nothing wider. Business accounts, artwork proofs and reorders were a planned second phase; third-party integrations and any AI feature were a third. Neither is presented here as delivered, and this project claims no AI feature. That boundary is why the work fits into 20 to 25 working days: one flow, a few product groups, an existing store and an acceptance test.
No measured result exists
No measured business result exists for this project and none is published here. The documents record scope and a duration; they record no conversion, order-value or production-time figure, and nothing is borrowed from another project to fill the gap. The 20 to 25 working days is what the work took, not what it achieved.
The client is named here on Netbase's own authority, recorded in the claim register on 25 September 2026. No consent from this client is on record, and no confidentiality obligation covers the project. If the client asks not to be named, this record reverts to the anonymised form the register keeps for it; the methodology page carries the address for that request.
Questions buyers ask
Is 20 to 25 working days an estimate for similar work? No. It is what this engagement took on a store that already existed. A different catalogue or a wider first phase gives a different answer.
Why is there no result on this page? Because none was recorded. This site publishes a figure only where it is attested and carries its measurement period, and this project has none. The methodology page explains the rule.
Planning a first project this size?
Compare it with the other work records, which are larger, then submit a project brief describing the single flow you would start with. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform, so a brief this size is read by the team that would deliver it.