ELTA Courier Eshop integration: dispatch preparation and tracking

Start an ELTA Courier connection by confirming available services and the merchant account's technical access.

ELTA Courier publishes a customer program for voucher management and a shipment tracking service. Public material alone does not establish an identical API route for every merchant account. Request current integration instructions and access details from the provider before selecting a connector. Confirm which service applies to each destination because domestic and international shipments have different requirements. This discovery stage prevents development based on assumptions. It also makes the proposed scope reviewable: the merchant can see which dispatch steps are automated and which require an approved operational procedure.

Warehouse staff need valid recipient information and parcel data passed into the shipping process. Voucher numbers should be associated with orders in stable fields that support lookup and reprinting. Putting a shipping number in free text is insufficient for customer service and downstream automations. For multi-parcel orders, preserve each label's relationship to the relevant package. Customer notifications should begin when genuine shipment information exists, rather than when a generic delivery method is selected. A clear readiness state also prevents labels being issued while stock allocation or packing is still incomplete.

Changing the address in the store after dispatch preparation does not necessarily alter information already sent to the courier. Define a separate correction and verification process. Similar controls are required for unused printed labels and changed cash-on-delivery amounts. Tracking events should be mapped carefully to commercial order states; a temporary carrier event must not automatically cancel or complete an order. Staff need to distinguish a connector error from a real delivery exception and know whether the next action belongs to the warehouse, customer support or the carrier.

Agree the ELTA Courier scope after confirming technical access. Document whether the project includes creation, printing, tracking updates or only part of the dispatch process. A shipment view should preserve what support needs for lookup without re-entering data. For multiple parcels, staff see separate labels rather than one tracking value overwriting earlier ones. Tie recipient corrections to preparation state. This makes it possible to explain precisely which tasks are automated and which require carrier coordination, without claiming that public tracking establishes every required integration capability.

A bookshop splits a large order into two parcels. The operator confirms a separate weight and label for each package. The order displays both relationships so support cannot report complete delivery when only the first parcel has arrived. Withdrawing one package before dispatch updates that shipment task rather than the entire purchase. Confirm the available ELTA Courier technical route first. Any step not supported automatically is shown as an explicit warehouse responsibility. Customers receive useful parcel information instead of one tracking reference that changes whenever a second label is created.

Acceptance covers single and multiple packages, reprinting and address correction after preparation. References remain stable and a new label must not erase another parcel number. Test the actual print format used by the warehouse and customer-facing tracking. Record unavailable functions rather than displaying them as successful. Support checks whether every parcel can be found from its order and whether pending dispatch is distinguishable from a pending information update. Also verify that an interrupted preparation task preserves all established relationships and tells the operator which action remains unfinished.