QuotedPartDocs · ERP
Quotes into your ERP
QuotedPart quotes; your ERP keeps the order, job, schedule and books. This is how a quote gets from one to the other, for each system, with what is sent and what isn't. Every send is one-way: changes made in the ERP don't come back.
By system
- JobBOSS² (cloud)
- Send to JobBOSS² through ECI's JobBOSS² API: estimates with routing and material, and the quote. Step by step and field by field below.
- JobBOSS on your own server
- Export for JobBOSS downloads a SQL file that creates the quote with its lines, routing and material when you run it on the JobBOSS server. How to run it.
- ProShop
- CSV or Excel export, or the API and webhooks. The direct ProShop push is off until it's checked on a real ProShop instance (below).
- E2 Shop System
- On JobBOSS², which ECI calls the former E2 Shop, use Send to JobBOSS². On an older E2 SHOP or E2 MFG install, export the won order as CSV or Excel. Which output fits your E2.
- QuickBooks and any other system
- CSV or Excel export of the quote or the won orders, one row per part, or the API.
JobBOSS²
One send creates an estimate per part with its routing and material, and a quote with a line per part. Customers, work centers and vendors must already exist in JobBOSS²; QuotedPart picks from them. ITAR vault parts are never sent, and assemblies go as one part without routing. Where the JobBOSS² login is kept, and the rest: JobBOSS² integration.
For the clicks, from connecting the JobBOSS² API user to the quote number coming back, see Send to JobBOSS², step by step.
What goes where in JobBOSS²
The fields follow ECI's JobBOSS² Public API (EstimateCreate, RoutingCreate, MaterialCreate, QuoteCreate and QuoteLineItemCreate).
| QuotedPart | JobBOSS² field | Note |
|---|---|---|
| Estimate, one per part (only when the part number is new to JobBOSS²) | ||
| Part number | Part number (partNumber) | The estimate's key: an existing one is never changed. |
| Revision | Revision (revision) | When the part has one. |
| Part description | Description (description) | First 200 characters. |
| The customer you picked | Customer code (customerCode) | |
| Quantity breaks | Quantity 1 to 8 (quantity1 … quantity8) | The first 8; JobBOSS² keeps 8. Default quantities off. |
| Unit price at each break | Price 1 to 8 (price1 … price8) | Price locked (lockPrice), pricing unit EA, so JobBOSS² doesn't recalculate it. |
| Lead days at the first break | Lead time (leadTime) | |
| Routing on the estimate, one step per operation, then one per finish | ||
| Operation order | Step number (stepNumber) | 10, 20, 30 … |
| Inside operation | Step type WORK and Work center (workCenter) | The work center you picked; the step-type code is read from your routings. |
| Finish or bought-in service | Step type VEND and Vendor (vendorCode) | No time on the step; the vendor's cost is in the locked prices. |
| Operation name | Description (description) | First 100 characters. |
| Setup minutes | Setup time (setupTime) | In your minutes code, or in hours when your routings only use hours. |
| Run minutes per piece | Cycle time (cycleTime) | The base estimate; lower per-piece times at larger quantities are already in the locked prices. |
| Material on the estimate (only when you gave its JobBOSS² part number) | ||
| The material's JobBOSS² part number | Sub part number (subPartNumber) | Quantity 1, unit EA, on the first routing step. |
| Material cost per part at the first break | Unit cost (unitCost) | |
| Material name | Description (description) | |
| Quote, one per send | ||
| The customer you picked | Customer code (customerCode) | |
| The quote's contact | Contact name (contactName) | First 50 characters. |
| Expiry date | Expire date (expireDate) | When the quote has one. |
| Quote number and title | Notes (notes) | "From QuotedPart Q-1042: Bracket set". |
| Each part | Line item 1, 2, 3 … (lineItems) | Part number, revision, description, quantity, price and unit EA at each break. |
| The part's notes | Job notes on its line (jobNotes) | When the part has notes. |
ProShop, E2 and everything else
ProShop: what works today
QuotedPart has no live ProShop integration yet. A quote gets into ProShop today as a file or through the API:
- CSV or Excel fileWorks today
- Export to CSV or Export to Excel on the quote's ⋯ menu, or Export on Orders for won orders. One row per part: quote or order number, customer, contact, email, PO number, order and ship dates, line, part number, revision, description, material, finish, process, size in inches and mm, weight, quantity, unit price, line total, add-ons, due date, a routing summary, currency, ship-to and notes. Bring it into ProShop the way your shop brings in other files, or key it in; we haven't checked it against a ProShop import template.
- API and webhooksWorks today
- The quote.accepted webhook sends the order's lines, quantities, prices, PO and ship-to to your server when the buyer accepts, and GET /api/v1/quotes/{id} reads any quote's prices. Your own code or an integrator can create the customer PO in ProShop from it through ProShop's API.
- Direct ProShop connectionPush off
- Settings › Integrations › ProShop connects to ProShop 5.2.3 or later and checks what your instance allows, but sending orders is switched off until it has been checked on a real ProShop instance. When it's on, each order you push creates a customer contact and a customer PO. It doesn't send estimates or routings to ProShop.