A customer selects pickup-point delivery, moves to the next step and finds no payment methods. Or prepayment is offered for a shipment meant to be cash on delivery. In PrestaShop multistore, diagnosing these problems means checking the combination of shop, carrier, country, currency, customer group and module settings. Enabling a new delivery option is only one part of the work.
Where should you start before changing settings?
Write down the expected behaviour first. For each storefront, define the delivery country, available currencies, prepaid and cash-on-delivery scenarios, and the existing methods that must continue working. This becomes the reference for configuration and testing. Without it, an intentional restriction can look like a fault.
In one of our deployments, we introduced pickup-point delivery across two multistore installations. The storefronts differed in their markets, currencies and payment options. We prepared separate scenarios for the affected websites rather than assuming that one installation meant identical settings.
Multistore context: one shop, a group or all shops?
Check the administration context before saving. PrestaShop supports working on an individual shop, a group or all shops. The selection affects the scope of changes; the settings available also depend on the page and module. The official multistore interface documentation explains these contexts.
Do not rely only on a successful-save message. Reopen the settings for each affected shop. Check a storefront that was meant to remain unchanged as well. This can expose an accidental global change before a customer encounters it.
Distinguish carrier association from carrier configuration. PrestaShop documentation explains that associating a carrier with shops and giving it a separate price range are different operations. Shops requiring different price ranges may need separate carriers. A shipping module may also manage its own associations.
Why is an active carrier missing from the cart?
Delivery availability depends on settings and on the particular cart. Our diagnostic sequence covers:
- the carrier’s association with the right shop and its active status;
- the delivery country, its zone and its association with the shop;
- customer groups, product restrictions and eligibility of the whole cart;
- weight or price ranges, maximum dimensions and out-of-range behaviour;
- the carrier’s connection to the current module and shipment template.
A zone name alone does not establish which countries it contains. Likewise, a correct price for one light product does not prove the boundary weight or a larger cart works. The PrestaShop carrier documentation covers ranges and availability settings.
In our deployment, one cause of a missing new delivery option was its association with an older carrier module. Correcting the connection to the integration and templates actually in use allowed checkout testing to continue.
Prepayment and cash on delivery need coherent scenarios
If prepaid and cash-on-delivery shipping use different prices or rules, test them separately. The first scenario should offer the intended advance-payment methods. The second should use payment on receipt and pass the correct collection amount into the order and shipment.
The PrestaShop payment preferences guide describes restrictions by currency, country, customer group and carrier. The payment module also affects what is supported. Enabling a carrier in one table does not establish that all other conditions are met.
In one storefront, the delivery method was visible but no payment method remained for a Polish delivery address. Country and currency restrictions needed correcting for the appropriate methods. We also checked cash on delivery in EUR in other storefronts. We did not copy the payment list blindly from another installation: its shipping module did not support exactly the same options.
A pickup-point map is only the beginning
Check that the selected point survives navigation to payment and back to delivery editing. Then verify that it is saved in the order and passed into the shipment form. Cash on delivery additionally requires support at the selected point and the correct amount passed to the carrier.
During Sandbox testing, a point available on the map was rejected by the test shipment API. Comparing it with another point helped narrow down the problem. A label generated after manually changing the point in the shipment form did not prove the original checkout-to-shipment path worked. We recorded that scenario as a limitation instead of marking the whole test as passed.
The cash-on-delivery checks also covered the insurance settings required by the particular service used. This describes one implementation, not a universal rule for every carrier. Current requirements and limits must be checked for the selected shipping product.
Which tests are useful before release?
Create a short scenario matrix and run it for each storefront affected by the change. A minimum set includes:
- Prepayment: the intended delivery method, charge, retained pickup point and correct payment methods, without unintended cash on delivery.
- Cash on delivery: the right delivery and payment-on-receipt method, matching order total and collection amount.
- Another country: a Poland-only method disappears for an address abroad while other delivery options remain available.
- Another currency: correct charges and payment availability, including after a currency change in the cart.
- Range boundaries: values just below, at and above the allowed weight or price threshold.
- Regression: existing couriers, payments and a shop outside the change retain their expected behaviour.
Reaching the payment-selection step verifies only that stage. Separately agree whether to create a test order, exercise payment notifications, create a shipment and inspect its label. Test environments need the appropriate Sandbox modes; production shipments and courier collections must not be triggered accidentally.
What did we actually verify in this deployment?
On test environments, we checked the affected storefront checkouts, prepaid and cash-on-delivery variants, currencies and the exclusion of delivery for a foreign address. Selected scenarios included a test order and a Sandbox label. We also documented the limitation affecting the particular test pickup point.
After test approval, we deployed the configuration to production and reopened the saved settings for the individual shops. Checks of the main production checkouts confirmed delivery visibility, retained pickup-point selection and the intended payment choices. We stopped before placing an order. We do not present that as an executed payment, a real shipment or a complete checkout test of every production storefront.
Our archive also contained a separate case where shipping-module configuration needed attention after a single shop became multistore. Installation history therefore belongs in the investigation. This is not a recommendation to uninstall a module or delete database records without analysis, backups and a recovery plan.
When do you need configuration, and when do you need code?
When associations, restrictions or templates explain the problem, start with configuration and tests. Additional code is appropriate when requirements exceed the capabilities of the installed modules, for example when service availability depends on the entire cart or a special business rule. Document the rule and include it in checks after updates.
Projectic combines store maintenance with integration work. Explore our technical support for online stores and our PrestaShop and WAPRO integration project. If a delivery or payment method disappears only in some shops, describe the problem: include the storefront, country, currency, delivery method and the step where the result changes. This makes the situation easier to reproduce.
This guide draws on the described deployment and PrestaShop 8 documentation. Screen names and module capabilities can differ between versions. Verify the behaviour on the version and module set used by the actual store.