Use this article when a calculated estimate is ready to leave GelatoConnect Estimator and become a job in your external MIS or downstream system. After this you will have pushed the estimate to the configured destination, captured any additional fields your MIS requires at handoff, and confirmed the transfer in the Export Log.
Before you begin
The estimate calculates successfully without blocking errors. If Calculate still shows a failure or a missing route, fix that first — export does not run on an un-calculable estimate.
An administrator has run Configure external MIS export for your print house. Connection enabled is on, Test connection has succeeded at least once, and the trigger list includes Manual if you intend to send by hand.
Steps
1. Open the estimate
Open the estimate from the estimates list. Confirm the price totals and the customer details match what you intend to send — the export payload reflects the estimate exactly as it stands now, including any rebates or manual adjustments on the price breakdown.
If you spot a discrepancy, fix it on the estimate before exporting. An export is not a draft; the MIS treats the payload as authoritative.
2. Select Export
Select Export in the estimate header actions. The Export to External MIS dialog opens and shows a job summary: Title, Product category, Quantity, Finished size, and Price. Review each line — these are the values the MIS receives in the payload.
The dialog reads Please double check and ensure that this is the order you want to export. If the summary does not match the estimate page, close the dialog and re-open the estimate to confirm what changed.
3. Fill in additional fields
If your administrator added additional export fields (e.g., PO Number, Cost center, Due date), they appear in the dialog with Required field or Optional field markers. Required fields block confirmation until populated; optional fields can be skipped. The Type of each field — Short text, Long text, Number, or Date — determines what value the dialog accepts.
If a required field is missing the value the MIS expects, ask the customer or your sales rep before sending — a placeholder will route the job to the wrong record downstream.
4. Confirm export
Select Confirm export. The dialog closes and a success toast reads This estimate is currently on the way to External MIS. The estimate is now in flight to the configured Destination URL.
If the connection rejects the request, the toast reads Error converting order with a short message. Open Why an export failed to diagnose.
5. Confirm in the Export Log
Open Export Log from the estimates area and locate the entry for this estimate. A successful transfer shows Success; a failed one shows Failed with the response the MIS returned. The log is the source of truth for what the MIS actually received — refer to it before re-sending or escalating.
Things to know
Export is hidden when Connection enabled is off, when no manual trigger is configured, or when your role does not include export permission. Ask your administrator if you cannot see the button on an otherwise valid estimate.
Re-exporting an estimate that already exported may prompt for confirmation. This is an intentional guard against creating duplicate jobs in the MIS — say no unless you really intend to re-send.
The customer-facing quote PDF is a separate surface from MIS export. The PDF reaches the customer; the JSON payload reaches the MIS. See How the quote letter works.
Automatic exports — driven by status triggers like Quote: Won — record an entry in Export Log just like manual exports, even though no estimator clicks Export. Review the log when an estimate flips into a trigger status to confirm the automatic send went through.
