Integrations
Connect accounting, drawings and the shop floor through handoffs that preserve the job and its history.
Plan connections around the systems your shop already uses. Job Shop Management has an authored application specification; each automated connection needs an agreed mapping, supported actions and tested recovery before it becomes part of the operating workflow. Manual document exchange can support an initial rollout.
- Accounting and payroll
- AccountingInvoices, Payments · out
- Supplier differencesin and out
- Payroll hoursout
- Drawings and shop instructions
- Drawings and modelsin and out
- CAM and setupin and out
- Labels and documentsin and out
- Customers and suppliers
- Customer portalsin and out
- EmailInvoices · in and out
- Outside processorsin and out
- Floor and shipping
- Terminals and scanningin and out
- Machine monitoringin
- Carriersin and out
- Agents
- Your agentWorks within the permissions you assign
Accounting and payroll
- Accounting. Map issued invoices, effective credits, payments and job-cost summaries to the accounting package. Supplier payables and the general ledger remain there. Preserve destination references and acknowledgments so a repeated period export cannot post the same transaction twice.
- Supplier differences. Reconcile supplier invoice differences against the purchased and accepted work. An authorized linked cost correction retains the original receipt price and the reason for the difference.
- Payroll hours. Export approved labor allocations with employee, work date and time category. Machine hours are separate. Reconcile payroll and attendance requirements before choosing how these job hours are used.
StatusSentPartiallyPaidOverdue
Drawings and shop instructions
- Drawings and models. Retain the exact reviewed drawing revision with the quote and released traveler. A changed external file must not replace the instructions for work already released.
- CAM and setup. Carry program identifiers, setup sheets, inspection requirements and operating instructions through the approved routing copy. Machine-program transfer needs a separately agreed device connection and operating procedure.
- Labels and documents. Define traveler, material, remnant and shipping layouts with the identifiers the shop actually scans. Reprinting preserves the revision and avoids creating a new stock or shipping event.
Customers and suppliers
- Customer portals. Start with RFQ, PO, change-request and delivery-document mappings. A portal revision becomes a reviewed request; it cannot silently change released quantity, price or drawing revision.
- Email. Configure recipients, approved document versions and delivery evidence for offers, acknowledgments and invoices. A failed or uncertain send remains available for reconciliation.
- Outside processors. Exchange dispatch details, operation-specific promises and return certificates. A returned lot keeps its dispatch lineage and must pass the applicable receiving requirements before its quantity becomes available.
Floor and shipping
- Terminals and scanning. Validate the chosen barcode, terminal and user mapping. A scan may identify work or prepare a ticket; actual clocking, quantity submission and approval still follow the configured actions.
- Machine monitoring. Treat imported machine signals as evidence requiring the agreed allocation and confirmation rules. Device messages do not establish an employee’s labor time or pass an inspection by themselves.
- Carriers. Agree label, dispatch, tracking and cancellation behavior with the selected service. Label creation is separate from confirmed shipment, and a repeated callback must not consume another quantity.
How connections are governed
service accounts, audit, pausingEach connection uses a scoped identity and preserves the source operation, payload identity and destination result. ShopEvents protects local effects; ShopDeliveries records each external handoff, including uncertainty and retry decisions. Review authorization, reconciliation and recovery with the actual provider before enabling automation. Availability of a platform interface alone does not establish a working connector.
The API is one more client of the same interface. Agent and API →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Prepare a quote from this RFQ and flag assumptions for the estimator.
› List outside dispatches with overdue or unresolved return quantities.
› Find submitted tickets whose labor allocations overlap.
› Prepare the close review with unresolved costs and billing obligations.