We Print All, South Africa: apparel, cards and signage in one print store
We Print All is a South African store selling apparel, business cards and signage from one catalogue. Netbase JSC's records hold a custom web-to-print engagement from October 2023 to June 2026, covering an online designer, pricing and PDF output. On 2026-10-07 the store returned a server error, so this record carries no live link today.
Start a project brief Explore servicesReviewed by CEO, Netbase JSC · Updated 7 Oct 2026
Who is We Print All and what market does it serve?
We Print All is a South African print shop operating from a single store at weprintall.store, selling apparel, business cards and signage. Netbase JSC's project records describe a custom web-to-print engagement covering an online designer, pricing logic, print-ready PDF output, storage and file handling, and storefront UI and navigation, dated October 2023 to June 2026.
The businesses named in these case studies are Netbase JSC clients; the web-to-print work described was delivered or designed by Netbase JSC, which operates Web2Print Solutions. Names, links and screenshots are shown with the operator's authorization and removed on request.
- Client
- We Print All, South Africa
- Status
- Delivered (store unreachable at check), checked by Netbase JSC on 2026-10-07
- Store
- weprintall.store; not reachable at today's check (see below)
- Platform
- Not visible in today's check; the store returned a server error on every path tried
- Products
- Apparel, business cards and signage (Netbase JSC project record)
- Work by Netbase JSC
- Online designer, pricing logic, print-ready PDF output, storage and file handling, and storefront UI and navigation
- Engagement period
- October 2023 to June 2026, about 2.7 years of dated, project-specific work
- Milestones
- Nine project-specific milestones and eighteen tasks, plus one milestone in a second, smaller record for the same store
Netbase JSC's own dossier recorded the store answering normally as recently as 2026-10-06, under the same browser user agent used for this review. Checked again from Hanoi, Vietnam on 2026-10-07, the homepage, robots.txt and two catalogue paths each returned an HTTP 500 server error with no page content, repeated over several minutes. That is a live server fault on the store's own Apache host, not a parked or closed domain, so this page does not use the "store no longer online" label it would use for a confirmed closure. It also publishes no language, design or upload step observed today, because none could be confirmed.
How big is South Africa's apparel, card and signage print market?
South Africans spent an estimated R159 billion online in 2026, with online retail crossing 10% of total retail turnover for the first time, per World Wide Worx's "Online Retail in South Africa 2026" report, published 2026-09-02. Clothing is the category most South African online shoppers buy: the same report found 36% of adults buy garments online, ahead of every other tracked category. For a shop selling apparel alongside cards and signage, that category alone carries much of the online buying habit the rest of the catalogue has to earn.
Printing SA, the industry body for South African printers, packagers and signage firms, put the country's printing and packaging industry at about R129 billion in 2025, with commercial printing the largest standalone segment at roughly 31% of market value. A shop selling business cards and signage sits inside that segment, against firms many times its catalogue's width.
What business problem does a multi-product print shop like this have to solve?
A shop selling apparel, business cards and signage from one storefront runs three production problems behind one basket. Apparel needs a decoration method plus size and colour variants before a price can show. A business card needs a fixed-size layout with bleed and trim set correctly. Signage needs a size and material choice where a mismatch is costly to redo. A generic "add to cart" button cannot carry all three without hiding an option a buyer needs or showing another options that do not apply.
The second constraint is checkout consistency: a buyer ordering T-shirts, a card re-print and a yard sign in one session expects one cart, not three flows bolted together. Netbase JSC's task record names an online designer, a pricing fix, PDF output work and storefront UI work as separate, dated items - evidence the design, price and production path was built, and kept working, as one system across all three families.
What decisions and trade-offs shaped the project?
-
Integrating third-party and API connections early, not wiring every family by hand
Two "Integrate: third-party and API integration" milestones closed within weeks of the online designer being added, between October and November 2023, rather than a separate connection per family.
-
Shipping a dedicated online designer at launch, not a plain order form
The same window closes an "Add: online designer" milestone, rather than launching with static products and adding design later. Apparel artwork, card layout and signage sizing are three different inputs a generic form cannot carry.
-
Treating a pricing-logic defect as its own fix, not folding it into general maintenance
A "Fix: pricing logic" milestone closed August 2024, separate from the general-scope fixes around it, rather than bundled into the next update. Each family prices on different inputs, so a pricing defect is worth fixing on its own.
-
Returning for plugin and theme maintenance years after launch, not leaving the build static
The most recent milestone, closed June 2026, is scoped "Fix: plugin and theme maintenance", rather than leaving the 2023-2024 build frozen. The layer under a designer and pricing engine ages, and a catalogue still taking orders needs it current.
How does an order move from catalogue to production file?
A generic architecture for this catalogue, built from the task record rather than a browse of today's unreachable storefront, moves an order through four stages.
- Choose apparel, cards or signage The product catalogue groups orders into these three families before any design step opens.
- Open the online designer Netbase JSC's task record names an online designer added in October 2023 and revisited again in October 2025.
- Set options and pricing Decoration method, size, quantity and material feed the pricing logic the record shows was fixed in 2024.
- Check that the file passes before print A file that does not pass the print-ready check is returned for a fix rather than reaching production; a file that passes moves to the production queue.
-
Product options
Decoration method, size and colour for apparel; layout for business cards; size and material for signage
-
Price inputs
Product, quantity and the option set per family; a 2024 milestone fixed the pricing logic
-
Artwork rules
Customer-entered artwork handled by the online designer, named in the 2023 and 2025 task record
-
File output
A print-ready file; PDF output work recorded in both 2024 and 2025
-
Integrations
Third-party and API integration completed October 2023; storefront UI work recorded in 2025
The failure modes this build guards against are the ones its task record names: a pricing rule returning the wrong total, a print-ready file that fails to generate, and storage or file-handling faults that lose an uploaded design before production. Each is its own dated fix rather than one undifferentiated "bug" entry. Storage and file handling work is recorded in 2025.
Netbase JSC maintains reusable web-to-print components - a browser-based online designer, rule-based print pricing templates, print-ready PDF output with CMYK conversion, bleed and trim, storefront connectors for WooCommerce, Shopify, Wix and custom stores, and a photobook editor - which an engagement may reuse under their own licence terms. The catalogue, pricing and production belong to We Print All.
(opens the full-size diagram in a new tab)
What was delivered over time?
-
2023, Q4 (Oct-Nov)
Two "Integrate: third-party and API integration" milestones and an "Add: online designer" milestone, closed the same window, then a "Customise: general scope" milestone by late November.
-
2023, Q4 (Dec)
A further "Fix: general scope" milestone, closed mid-December.
-
2024, Q2 (May-Jun)
A "Fix: general scope, customisations retained" milestone, closed early June.
-
2024, Q3 (Jul-Aug)
A dedicated "Fix: pricing logic" milestone, closed early August.
-
2025, Q2 (May)
The second, smaller product-development record closes its own "Fix: general scope" milestone.
-
2026, Q2 (Apr-Jun)
"Fix: plugin and theme maintenance", closed June 2026, the most recent record.
Seventeen of twenty-seven milestones across the two project records are a shared scaffold, not delivered scope; this timeline lists only the ten project-specific items.
What does this record show, and what does it not?
It shows a South African print shop running apparel, business card and signage products from one catalogue, with dated task and milestone records covering an online designer, pricing logic, print-ready PDF output, storage and file handling, and storefront UI work, from October 2023 to June 2026.
It does not show order volume, conversion or any revenue figure; none is measured to a published method and none is claimed. It does not show the store's current design, language or upload step, because the store returned a server error on every path checked on 2026-10-07, despite answering normally the day before; this page carries no screenshot and no working link, and does not show which parts of today's unreachable storefront predate these records. Web2Print Solutions is the web-to-print engineering service of Netbase JSC. Delivery records cited on this site belong to Netbase JSC; where no delivered example of a capability is published, the page says so rather than implying a record.
What should a print business in this niche take from it?
-
Treat each product family's options as its own data model
Apparel decoration, card layout and signage size and material do not share one option set.
-
Fix pricing defects as their own priority, not general maintenance
A wrong total on one of three families is a different risk than a cosmetic bug.
-
Keep the design and file-output layer under maintenance, not frozen at launch
Plugin and theme work returned about two and a half years after the first release window.
-
Separate what a dated record shows from what a live browse would add
A delivery record and a working link are different kinds of evidence; a server error today does not erase the first.
Key takeaways
- We Print All is a South African store selling apparel, business cards and signage from one catalogue; Netbase JSC's project records run from October 2023 to June 2026.
- The record names an online designer, pricing-logic fixes, print-ready PDF output, storage and file handling, and storefront UI work as separate, dated items.
- Checked again on 2026-10-07, the store returned an HTTP 500 server error on every path tried, despite answering normally the day before; the label on this page reflects that, not a closed store.
- No order volume, conversion or revenue result is claimed for the store.
How could a similar project start?
If you run a print shop selling more than one product family from one storefront, send a project brief listing each family's option set (decoration method, layout or material), whether pricing already differs by family, and which part of your build last had a dedicated fix. Apparel decoration routing is covered on apparel and promotional print, with option rules on the T-shirt designer and business card editor pages, and signage sizing on the banner and signage configurator. General option-rule engineering sits under print product configurator, and pricing work like the fix in this record is covered on print pricing engine. A related multi-product record is the Printomatic case study in Canada; every case study is indexed on the evidence hub.
Frequently asked questions
No. Netbase JSC's project record lists three product families: apparel, business cards and signage, sold from one storefront.
Every path checked on 2026-10-07 returned an HTTP 500 server error, repeated over several minutes, even though Netbase JSC's own dossier recorded the store answering normally the day before. A server error is a different finding from a parked or closed domain, so this page uses that label rather than "no longer online" or an unconfirmed live link.
The project-specific records describe an online designer, pricing-logic fixes, print-ready PDF output, storage and file handling, and storefront UI and navigation work, not a single from-scratch build narrative.
Both mix signage with other product families from one storefront - Printomatic adds real-estate signage and business cards to large-format print, We Print All adds apparel and business cards to signage - but the two are different shops in different countries.
References (4)
- Netbase JSC project records for weprintall.store (custom web-to-print engagement, nine project-specific milestones, eighteen project-specific tasks, October 2023 to June 2026) and a second, smaller product-development record for the same store (one milestone, May 2025), reviewed 2026-10-07.
- Read-only check of weprintall.store (homepage, robots.txt and two catalogue paths) from Hanoi, Vietnam, each returning an HTTP 500 server error, repeated over several minutes on 2026-10-07.
- World Wide Worx, "Online Retail in South Africa 2026", published 2026-09-02, worldwideworx.com/onlineretailsa2026, accessed 2026-10-07.
- Africa Print, "Printing SA Discusses The State Of The Printing Industry" (reporting Printing SA industry data), published 2026-02-26, africaprint.com, accessed 2026-10-07.