Product 03

Built for the largest
operations in the industry.

Enterprise solutions that keep you ahead of a fast-moving shift in technology, built on top of your existing tech stack.

What it covers

Five things, and they
build on each other.

InkIQ Agents do the work inside your business. InkIQ Intelligence is what your data becomes so the rest of the market's software can use it — for manufacturers, wholesale suppliers and anyone whose products are sold through somebody else's systems.


01 — Structure

Software is choosing
products now.

Decorators and distributors are wiring agents into their inboxes — agents that read a customer email and recommend the blank. Those agents can only choose from what they can read, and most catalogues say "t-shirt, 100% cotton, S–3XL" and stop. A product with no imprint data doesn't lose the comparison. It never enters it.

  • Imprint locations tagged per style with maximum dimensions for each — front, back, left chest, sleeve, hood, neck label
  • Which decoration methods each product genuinely suits, and which it doesn't
  • Fabric weight, construction, stretch, pilling and shrinkage as data rather than prose in a PDF
  • Use cases and industries, so an agent knows when to reach for it
  • Comparable styles mapped across your own range, so a stock-out sends the agent to another of yours instead of a competitor's
  • Size charts and colour values machine-readable, so mockups render true and colours render right

Done by the same tagging engine that already runs inside InkIQ, not by a room of people with a spreadsheet.

Style 4471 · before and after
What the catalogue says today

Heavyweight tee · 100% cotton · S–3XL · 14 colours

What an agent needs
Fabric270 gsm · ring-spun
Front centremax 14 × 16 in
Left chestmax 4 × 4 in
Best forScreen · DTF · embroidery
Not suitedSublimation
Comparable4390, 4412 · same hand
Size chartMachine-readable

02 — Distribute

We build the API
your customers plug into.

Right now your images, spec sheets and product data go out as emailed zip files and PDFs, and the version running on a distributor's site is two seasons old. We build and maintain one live API — your products, your imagery, your specs — that your customers' systems read directly.

  • One endpoint for every image, on-model shot, flat lay and swatch, instead of a zip file someone has to request
  • Spec sheets and care instructions as structured data, not a PDF a human has to read and retype
  • Versioned, so a discontinued colourway stops appearing across the channel instead of lingering for a year
  • Carries the tagging from 01, so your customers get one integration rather than two
  • Maintained as the range changes, each season, rather than handed over and left to rot
Product API · style 4471
On-model14 colourways · 4 anglesCurrent
Flat lay & swatchfront, back, detailCurrent
Spec sheetstructured · not PDFCurrent
Sand colourwaydiscontinued 14 JulWithdrawn
Reading this API38 distributors

Withdrawn products disappear from every downstream site automatically. Nobody has to be emailed.


03 — Answer

The document hunt
that holds up orders.

Test reports, fibre content, Prop 65, care labelling, social compliance audits, sustainability certifications. Every large customer asks for a different subset in a different format, usually mid-order, and somebody goes digging through a shared drive while the order waits.

  • Every certificate, test report and audit indexed against the styles and factories they cover
  • Requests answered immediately with the correct current document, not the one someone remembered
  • Expiry tracked, so you find out a certificate has lapsed before your customer's compliance team does
  • Recurring vendor questionnaires filled from what you have already answered elsewhere
  • Anything requiring a signature or a legal position goes to a person — it gathers, it doesn't attest
Document request · account 1180

“Before we release the PO we need current test reports and your social compliance audit.”

Fibre content · 4471issued 03 FebSent
Prop 65 statementissued 11 JanSent
Social compliance auditfactory 04 · expires 22 SepExpiring
Answered inUnder a minute

The expiring audit was flagged to your compliance lead the same morning, six weeks before anyone would have noticed.


04 — Connect

Oracle stays.
SAP stays.

You did not buy a seven-figure ERP in order to replace it, and we are not asking you to. This is a layer above what you run: it reads from your systems, structures what comes out, and writes finished records back where they belong.

  • Built onto the ERP, PIM and asset library you already have — your system stays the system of record
  • Every engagement starts by mapping your stack, not by asking you to export it
  • Custom integrations where the connection doesn't exist yet
  • A dedicated developer on the account, so the person building it knows your data model
  • No migration, no rip-and-replace, no eighteen-month programme

This is scoped work with a written statement of work, which is why it starts with a call rather than a signup.

Your stack · mapped
ERPsystem of record · unchangedReads
Product datastructured & enrichedWrites back
Asset libraryindexed & versionedWrites back
Document storecertificates & reportsReads
Customer systems38 distributorsServed

Nothing migrates. If you switch us off, your systems are exactly where they were.


05 — Read back

You see orders.
You don't see demand.

By the time a purchase order reaches you, the decision was made weeks earlier — by a decorator quoting a job for their own customer. We sit in the communication and quoting layer of those print shops, which means we see what the end customer actually asked for, not just what eventually got ordered.

  • Built from the transactions themselves — the enquiries, quotes and orders moving through the network, not a survey circulated after the fact
  • End-customer demand read from the print shop's inbox and quotes, weeks before it becomes a purchase order
  • Category, weight and colourway movement across the season, with direction rather than a single number
  • What was asked for and couldn't be filled — the demand your competitors also missed
  • Benchmarks on lead time and fill rate against the wider market
  • Reported as market movement, never as a named company's figures — nobody sees what any individual business did

Nobody else can build this. It comes from sitting in the communication and quoting layer of the print shops themselves — the email, the question, the quote — instead of counting shipments months after they happened.

Channel demand · this season
Heavyweight
Fleece
Performance
Lightweight
+31%
Fleece specified
18%
Asked, unfilled
4.1d
Your lead time
5.6d
Market median

Market-level movement. No individual company's figures are ever shown.


How the data works

The part most vendors are vague about

The work moving through InkIQ is what teaches the system to do this job well, and market intelligence is a product of that same position. We'd rather say so plainly than bury it. What it does not mean is that your business becomes visible: your customer list, your pricing, your margins and your artwork are never shown to another company, never sold as a record, and never reproduced as output outside your account. What improves is the system's judgement. What stays private is your business.

All of it is written into the agreement, not just onto this page.


Who buys this

For the companies whose products
are sold by somebody else.

If your goods reach the market through distributors, dealers and decorators, their software is now deciding what gets specified. This is how you stay in that decision.

Every build is scoped.

We map your stack, agree what gets structured and what gets served, and put it in writing before anyone starts. It begins with a call rather than a signup, and the first thing we look at is the state of your product data.

Talk about your data

Watch it do the job.

Send us one real enquiry — the email, the purchase order, the artwork, the messy bits — and we'll run it through the agents in the first ten minutes of the call. That's a faster argument than anything we could write here.