ERP integration or spreadsheet export: planning a quotation pilot

When is an export enough?

An export can quickly test whether interpreting material lists and matching them to your catalogue creates value. It can be a useful starting point when data freshness is controlled and transferring the reviewed draft does not add more work than the workflow saves.

Give the export an owner, version and validity period. If pricing differs by customer, establish that in the sample. A list price is not automatically the net price that may be offered to a particular customer.

When do you need an integration?

Frequently changing prices, customer-specific discounts or direct draft handover may require a system connection. Check read and write permissions, error responses, field limits, currency and unit conversions.

A repeated request must not create duplicate quotations. After an interrupted transfer, the team needs to know which records arrived and which still require a retry. Verify the connection in an appropriate environment of the actual target system before production launch.

The initial Tételív pilot scope

The pilot costs £750 ($950 in the US), excluding VAT where applicable. It covers one catalogue and price source, up to 100 requests and 2,000 line items in total. The planned measurement period is 10 working days after receipt of a complete, usable sample package. This is not a blanket promise to complete every ERP integration within ten days.

The full rollout fee is £2,950 ($3,790) in total, including the pilot fee, so £2,200 ($2,840) remains after the pilot. On a 24-month term there is no setup fee and the monthly fee is 20% higher. Go-live, the specific integration and ongoing operation are agreed in writing. If you do not need a system connection, Starter (£99 a month) or Team (£349 a month) start with no setup fee, and Quick start (£449, $579 one-off) loads and maps your catalogue and up to 3 supplier price lists from files.

Before accepting the handover

1. Document field mapping and the source data version.
2. Confirm that missing products, prices and units trigger visible stops.
3. Have the designated reviewer check the sample drafts.
4. Verify that transferred records appear in the target system if transfer is in scope.
5. Agree error handling, access rights and rollback.
6. Decide whether to proceed using measured benefits and remaining manual work.

A successful login or an exported file alone does not prove that the integration works through to the destination.

Frequently asked questions