TecCom integration: a step-by-step guide

TecCom is TecAlliance's B2B commerce platform. Through a single integration, you access 280+ suppliers in the European aftermarket: availability queries, price lookups, electronic ordering, confirmations, delivery tracking.

The classic alternative is direct integration with each warehouse via API, CSV, or email. It works for 2-3 suppliers. Above 5, it becomes unsustainable: each warehouse has its own format, its own update schedule, its own SLA. TecCom normalizes all of that into one stream.

You cannot use TecCom without a license from TecAlliance. The license is signed annually and cost depends on query volume, number of activated suppliers, and distribution model.

Across the EU, TecAlliance partners can broker the licensing and configure access to the TecCom sandbox for development. This step takes 2-4 weeks. Plan ahead.

You also need each supplier's consent to communicate via TecCom. Some relationships are active by default (TecCom lists the supplier), others require separate activation with the supplier.

TecCom uses API key plus session token authentication per supplier. Your platform keeps credentials in a secure vault (not .env plain), and refreshes sessions on expiry.

For each activated supplier, you configure the TecCom partner ID, endpoint address, and routing rules (which SKUs go to which supplier). In the TecDoc catalog, every part has a "mapping" to one or more available suppliers.

When a customer lands on a product page, the platform makes a TecCom call for availability and price. The response is near-instant (under 500ms in normal conditions) and includes: stock per warehouse, net price per supplier, estimated delivery time.

Important detail: do not query TecCom on every product page in real time. Use aggressive caching (30-60 seconds per SKU) and background refresh. Otherwise you end up paying for thousands of calls per day and degrading shop latency.

I recommend the "cache-first with background refresh" pattern: display from cache immediately, fire the call in background for refresh, invalidate cache when the order is placed.

Orders are placed through TecCom in TXML5 format (standardized XML). Your platform composes the message (items, quantities, delivery preferences), signs it, and sends it. TecCom returns an order ID, the supplier's confirmation, and a delivery estimate.

Error handling is critical. The supplier can reject the order (insufficient stock, blocked account, invalid SKU). The platform must surface these cases visibly to the operations team, not silently.

After placement, TecCom offers webhooks for status updates (confirmed, in preparation, shipped, delivered, delayed). You process webhooks on a queue worker, not synchronously.

TecCom uptime is good, but incidents happen (auth issues, timeouts, suppliers temporarily offline). Your platform needs to know quickly when something isn't working.

Set alerts on: TecCom call error rate above 5% in a 10-minute window, average response time above 2 seconds, unprocessed webhooks in queue above 100.

Structured logging for every call (request/response, latency, result) saves you hours of debugging when a supplier complains about a missing order.

Test on TecCom sandbox with real data (suppliers can configure a test endpoint). Place 5-10 test orders, monitor webhooks, run an error scenario (supplier rejection, timeout).

Production rollout is gradual: activate one supplier first, monitor for 48 hours, then add 2-3 more, and so on. Do not launch with 60 suppliers simultaneously.

Document the onboarding procedure for each new supplier. Within months, you will have a structured list: TecCom credentials, supplier contacts, agreed SLA, SKU mappings. Without documentation, adding each new supplier takes a day instead of an hour.

Hardcoding the supplier list in code. When you want to add a new supplier, it requires a deploy. Correct: config table in the DB, admin UI for activation/deactivation.

Not calculating margin during the query. You display the net price from the supplier instead of the final price with markup. Customers order, you discover the difference at invoicing, you are in the red.

Ignoring caching. The shop makes 5000 calls a day when it should make 500. Costs go up, latency drops.

No fallback plan when TecCom is unavailable. The shop shows "error" instead of "last known stock and price, refreshing". UX suffers unnecessarily.