MaltaPost publishes an eSeller dispatch workflow and a web service for shipping-rate estimates. Do not assume those pages establish a publicly available API for every label, booking or tracking operation your shop needs. Confirm the exact integration with MaltaPost before commissioning automation.
Separate the published services
The eSeller page describes registration, entering parcel details, generating labels and booking collection or dropping items off. The web-services page describes delivery choices and estimated shipping charges. These are useful starting points, but a customer-facing feature description is not a complete developer contract.
Ask your business contact for current technical documentation, account access requirements, supported operations, test access and service limits. Obtain confirmation of the specific integration you intend to build. A plugin mentioning MaltaPost may be unofficial or may support only part of the workflow.
Map the dispatch task before automating it
Follow one real order from payment to packing and delivery. Identify who confirms stock, weighs the parcel, chooses the service, prints the label and checks that the parcel leaves the premises. Note where staff currently retype information and which mistakes cause support requests.
Separate shipping-price estimates from actual fulfilment charges. Dimensions, weight, destination and service restrictions can affect what is appropriate. Decide how the store handles products that cannot travel together, an address that fails validation or an order that exceeds the configured parcel assumptions.
Make order and parcel records match
Use a stable internal order reference and record the external parcel/tracking reference when available. If label generation or booking is retried, the system must not silently create duplicate consignments. Give staff a way to see whether an operation succeeded before repeating it.
Keep credentials on the server and use only documented interfaces. Do not expose an account login in JavaScript or scrape a portal as if it were a supported API. If direct integration is not available, an accurate export and a controlled staff workflow may be safer than fragile automation.
Plan customer communication and exceptions
Tell customers the delivery options and expected dispatch process before checkout. Distinguish dispatch from delivery and avoid presenting an estimate as a guarantee. Provide the tracking reference when it is valid, and decide who handles an incorrect address, returned parcel or lost-item enquiry.
Keep personal data transfers proportionate. A carrier may need delivery information, but it does not need your entire customer profile or unrelated enquiry history. Document the fields sent and the reason for each. Check your privacy information and service arrangements with appropriate advice.
Use a staged acceptance test
Start with a small set of representative orders: local delivery, international delivery if offered, unusual weight, cancellation and a retry after a connection failure. Verify the actual output with staff and the carrier before enabling it for every order. Keep a manual fallback for service interruptions.
Before approving development, ask for a written list of supported actions and the provider evidence behind them. Then include dispatch requirements in the wider online-store launch checklist. A clear integration boundary is more valuable than promising that an API will eliminate every manual step.
Sources and review
Official references checked on 18 October 2026. Provider terms, funding calls and technical documentation can change; verify the applicable version before committing to a purchase or application.
Your next step
Need a website that works as hard as your business?
We design clear, fast and responsive websites for businesses in Malta. Tell us what you are planning and we’ll reply with practical guidance.
Get a free consultation