Redeveloping a large-format print store over more than a year
Netbase redeveloped the user experience, the interface and most of the system behind the online store of a large-format inkjet printing company in Singapore, across several phases and more than a year. The client is not named. No launch date, figure or business result is published here, because the source records none.
Submit a project See all work records
Record at a glance
- Evidence level
- Portfolio record: delivered scope, no result published
- Client
- A large-format inkjet printing company in Singapore; not named
- Service
- Custom Product Engineering
- Delivered scope
- Redeveloped user experience, interface and most of the store system, with custom functions built to the client's specifications
- Shape of the work
- Several phases over more than a year
- Published results
- None
What an engagement of this length actually is
This was not one rebuild handed over once. The client wrote its own workflow, design, back-end and front-end specifications, and Netbase built against them phase by phase. Over more than a year that has a consequence worth naming: the specification and the running store move together, each phase changing what the next one is for.
The platform the store runs on
A WordPress print-store feature set carried the catalogue, the accounts and the ordering path. Everything the client's workflow needed that a standard print store does not do was built as custom functions on top of it, which is why a store this specialised did not need a platform written from nothing.
The function a buyer remembers: a multi-page PDF mapped to product sides
Large-format buyers usually arrive with artwork already made, as a PDF, often with more than one page in it: one per side of a double-sided banner, per panel of a display, per face of a printed board.
Before this function existed, the online designer could not take that file. The shopper had to export each page as an image, upload them one at a time, and remember which page belonged to which side. Every one of those steps is a place to make a mistake that nobody notices until the job has been printed.
The custom function moves that work into the store:
- the shopper uploads the PDF straight into the online designer;
- each page is converted to a high-resolution image that can be edited on the design canvas;
- a low-resolution upload raises a warning before the order is placed rather than after the press has run;
- the pages of a multi-page PDF are mapped to the sides of the product in order, so each side can be picked in the editor.
The last point is what solves the problem. Order carries meaning in print: page one is the front, page two is the back, and a panel out of sequence is a reprint at somebody's cost. Mapping the pages in order, inside the store, removes the most expensive class of print error, the one found after production.
What no result means here
No measured result exists for this engagement and none is published. The source records delivered scope and nothing else: no launch date, no traffic, conversion or revenue figure, and no count of the client's printers, staff or premises. The cooperation was still running when the source was written, so even a completion date would be invented.
More than a year of work is a duration, not an outcome. It says the client kept commissioning phases; it says nothing about what the store earned.
Questions buyers ask
Why is the client not named? It is not on Netbase's list of clients who have agreed to be referenced. Its logo does appear in Netbase's own client strip, but permission to display a logo is not permission to attach a project to a name, so the record stays anonymised.
Does a year-plus engagement mean the first release took a year? No. The work ran in several phases, each with its own specification and delivery. How a phased engagement is planned and reviewed is set out on the project delivery page.
Can the PDF function be reused on another store? The pattern can: uploading a PDF into a designer, checking resolution and mapping pages to product sides is a design any print store can adopt. The implementation itself was built to one client's specifications.
Is any of this an AI feature? No. Nothing in this record is described as AI, and the source records none.
Planning a print store of this size?
Read the other work records, check how claims here are sourced on the methodology page, then submit a project brief naming the artwork formats your customers send you, because that decides more of the build than the catalogue does. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform, so the team that reads the brief is the team that would deliver the phases.