What API-ready agency orders look like in Tharstern

If you print for real estate agencies, you already know the pattern. Orders arrive as emails. Someone in prepress reads the message, works out the size, checks whether the artwork has bleed, keys the job into the MIS, and then emails back to ask which office it is going to.

What changes with a structured order

When agency orders come through an API, the job arrives as data rather than prose. A typical Ezi order carries:

• Print-ready PDF with the correct bleed and colour profile, generated from a template you never have to fix.
• Product and substrate: corflute, ACM, vinyl, poster stock, with size and quantity.
• Finishing and install instructions.
• Delivery address, whether that is the office, the property, or an installer.
• Agency, office and contact details for billing and queries.
• A job reference that both sides use for the life of the job.

Tharstern specifically

Where a partner runs Tharstern, Ezi can feed jobs directly into the MIS so the order lands as an estimate or job without prepress re-keying, and status callbacks flow the other way. When the job moves to production in your system, the agency sees it move in theirs. Nobody rings to ask.

If you do not run an MIS with an API

Nothing breaks. Orders arrive by email in the same structured format, and you can accept, update and dispatch jobs through the Ezi supplier portal. The agency still gets live status; you still avoid the back-and-forth.

The part that matters commercially

Ezi does not sit between you and your agency customers. They keep printing with you at your prices. What changes is the admin: fewer clarification emails, fewer reprints from wrong artwork, and a predictable stream of correctly specified jobs.