Integrating a carrier the market doesn't cover, or a specific shipping-cost rule
Parcel tracking, specific shipping-cost calculation, a carrier missing from the market of existing modules: what I build on the logistics side when the standard modules aren't enough.
The typical need
PrestaShop natively covers the most common carriers through off-the-shelf modules, but some needs fall outside their scope: a regional or foreign carrier with no module available, a shipping-cost rule that combines weight, volume and zone in a way the native rules can't express, or parcel tracking shown directly in the customer account rather than pointing to a third-party site. These needs come up regularly as soon as a store moves beyond the most standard delivery patterns.
How I approach this kind of work
The first step is understanding what the carrier actually offers on the technical side: an API for generating labels and tracking, a simple file export, or nothing programmable at all. This point largely determines the scope of the module to build. For a specific shipping-cost calculation, I start from the rules actually applied by the business rather than a theoretical simplification, with edge cases (bulky products, excluded destinations, free shipping above a certain amount) built in from the design stage rather than bolted on afterwards.
When parcel tracking needs to appear on the customer side, I make sure the information stays in sync with the real delivery status, refreshed at a rate consistent with actual usage — there's no point querying the carrier's API on every page view if the status only changes a few times a day.
Factors that affect the estimate
-
Availability of a carrier API
A carrier with a documented API for label generation and tracking makes development markedly simpler than a manual process that needs automating.
-
Complexity of the pricing grid
A simple weight-based rule is a different problem from a grid combining zone, volume, declared value and product exceptions.
-
Number of pickup points or zones
A pickup-point selector referencing several thousand locations needs a different search architecture from a simple list of zones.
-
Integration into customer tracking
Showing parcel tracking directly in the customer account, rather than a simple external link, adds synchronisation and presentation work.
Frequently asked questions
Can a carrier with no available API be added?
Can the module handle several carriers with different rules?
How are zones or countries not served handled?
Does a custom carrier module stay compatible with PrestaShop updates?
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.