Use this article when you need to understand how a calculated estimate leaves GelatoConnect Estimator and arrives in the system your shop already uses to run jobs. After this you will know which surface configures the connection, which surface triggers an export, where to find the history of past exports, and which role is responsible for each step.
What estimate export is
Estimate export sends the structured contents of a calculated estimate from GelatoConnect Estimator to a destination that your shop controls. The destination is most often a MIS, an ERP, a BI warehouse, or a custom job-ticket service that listens for a JSON payload at an HTTPS endpoint. Estimator is the quoting engine; the destination is where the quote turns into a job ticket, an invoice line, or a production run.
The connection is configured once per print house under Estimate Setup → Settings → Connections. From then on, an estimate either exports manually when an estimator selects Export on the quote, or automatically when the estimate reaches a status that the connection lists as a trigger.
A worked example
Northgate Press is a German commercial shop running an external MIS that already holds the company's price lists, customer records, and production scheduling. The MIS team exposes an HTTPS endpoint at a URL the shop owns, protected by a bearer token.
An administrator opens Estimate Setup → Settings → Connections for the print house, sets Export destination to External MIS, enters the Destination URL, chooses Authentication method Token, pastes the bearer token, and adds Triggers. They pick Manual so estimators decide when to send, and Quote: Won so an estimate that flips to won is also pushed automatically. They run Test connection to confirm the destination responds, then Save changes. The administrator adds two additional fields — PO Number (Short text, Required) and Cost center (Short text, Optional) — so estimators can capture the MIS metadata at handoff.
When an estimator finishes a quote for a 5,000-run Stitched Book on Silk 100gsm SRA1, they select Export in the estimate header. The Export to External MIS dialog opens, prompts for the PO Number and Cost center, and sends the JSON payload to the MIS endpoint with the bearer token attached. The estimator sees This estimate is currently on the way to External MIS, and the MIS picks up the job a few seconds later. The same estimate would have exported automatically when the quote flipped to Won.
What this affects
Estimate edit page — adds an Export button to the header actions on a calculated estimate, and lets administrators capture PO numbers, cost centers, and similar MIS metadata in the export dialog.
Estimate Setup → Settings → Connections — owns the destination URL, authentication, triggers, and additional fields. Changing these affects every future export from this print house.
Export Log — records every export attempt with its status. Administrators read this to confirm a transfer succeeded or to diagnose a failure.
What this does not affect
Quote letter — the customer-facing PDF and email are separate from MIS export. A quote letter never travels to the MIS connection, and an MIS export never produces a quote letter. See How the quote letter works.
Price calculation — export reflects the estimate exactly as it stood at the moment of export, including rebates and manual adjustments. Export does not recalculate or change any line on the price breakdown.
Estimator role — being able to export does not give the estimator permission to edit Settings → Connections. The connection editor is administrator-only.