Geniki Taxydromiki Eshop integration: vouchers and shipment finalization

Creating a voucher and finalizing shipments before carrier handover are distinct stages in a Geniki integration.

The official Web API V2 documentation describes a SOAP/WSDL service, test environment and production access. The required implementation includes authentication, voucher creation, printing, cancellation and finalization before live credentials are granted. A connector that only prints labels is therefore incomplete. Finalization informs the carrier branch about prepared shipments. Design must cover daily pending work as well as initial record creation. That distinction matters when staff prepare labels at one time and physically hand over parcels at another, or when some prepared shipments are withdrawn.

Persist the relationship between order, job and voucher number, and manage authentication keys according to their validity. Warehouse staff print the correct labels and confirm which parcels will actually be handed over. Then finalize the agreed period so work created on a previous date is not missed. Dates and times are operational data and require a consistent timezone. Store each stage's result so an interrupted job can resume without repeating successful steps. The user interface should clearly distinguish a created voucher from a finalized shipment ready for carrier reconciliation.

Day boundaries create a specific exception: a label may exist without being finalized when the calendar date changes. Staff need a pending report and a safe way to close the correct date range. A failed cancellation must never appear as successful on the order. When authentication expires, obtain a new key before retrying an eligible operation. Keep the sequence auditable so a connection incident does not become confusion during handover. Reconciliation should identify both missing finalizations and parcels physically packed but absent from the intended handover list.

For Geniki Taxydromiki, pay particular attention to creation versus finalization. Warehouse staff see labeled parcels that are not yet ready for handover. Daily work cannot depend solely on the current date because previous-day items may remain pending. Record who approves a batch and who handles cancelled parcels. The handover list must match the physical packages. This reconciliation helps identify an open shipment or an unused label early. Authentication recovery remains a technical concern, while deciding which parcels actually leave the warehouse remains an operational decision.

A spare-parts store prepares parcels in the evening and hands some over the next morning. Each job records voucher creation time and finalization state. The next-day list includes eligible open records without creating replacement labels. A withdrawn parcel is excluded from physical handover and its cancellation outcome is verified. Staff approve a batch matching the actual packages. Changing dates therefore does not hide outstanding work, and the morning process is not restricted to records created today. Preparation and finalization remain visible as separate operational stages.

Acceptance checks expired authentication, reprinting and finalization of records created on a previous date. Compare the list with physical parcels and identify open records that should not leave. A failed cancellation remains visible instead of appearing complete. Test repeated execution of the same batch and preserve a clear outcome. Staff approve label samples and the daily closing procedure. Production access follows the provider's approval process rather than being inferred from a successful test call. Recovery should show whether authentication, voucher handling or finalization remains the unfinished stage.