PrestaShop repairs, upgrades and development
Illustration of a discussion about handling store orders.
You can contact us about a broken part of the store, a problem following an earlier change, or a task your team still handles manually. For the first message, the store URL and a description are enough. We will agree how to arrange access separately.
Examples of our PrestaShop work
Ragazza: imports and a connection to business software
For Ragazza, we built product and image importers for the Ragazza and Gatta brands, an integration with Symplex Small Business, a description generator and tools for managing the catalogue.
See the work we carried out for Ragazza.
BUY-IT: wholesalers and price change history
We developed wholesaler integrations and a price change history system for BUY-IT. The work covered feeding the store's product range and making information about product price changes available.
Tempus: an engine upgrade and a custom module
For the new version of Tempus, we upgraded the store engine, changed the design and built a custom module for presenting products and categories.
What can we help with?
| Need | Possible scope | What we check before quoting |
|---|---|---|
| Store fault | Reproduce the issue, identify its cause and make the agreed fix. | Which action fails, when it started and what changed beforehand. |
| PrestaShop upgrade | Prepare the version change, try it on a copy and test the store. | Store engine, PHP, module and theme versions, plus custom modifications. |
| Module or theme | Adapt an existing component or build a custom feature. | Expected behaviour, dependencies and how to verify the result. |
| Product import | Add or update the agreed data and images. | Data source, identifiers, field mapping and error handling. |
| Integration | Exchange data with a wholesaler or software used by the business. | Available documentation, direction of exchange, and the source of prices and stock levels. |
| Slow performance | Measure the affected action and identify the cause of the delay. | When the store slows down, what the user is doing and which data affects the result. |
We plan each integration around the particular system and its capabilities. The portfolio confirms work we have completed; a new connection still requires a review of its documentation and data. Our system and API integration service explains this work in more detail.
How do we prepare a store upgrade?
- Review dependencies. We check PrestaShop, its environment, modules and theme, including changes made by previous developers.
- Agree the backup and test environment. We establish which files and database are needed and how to restore them. We plan to trial a major change away from live sales.
- Run the trial and tests. We check the agreed scenarios, such as a product variant, discount, order, payment, delivery and customer email. Acceptance checks cover phones and computers.
- Plan the switch. We agree the timing, how to retain new orders and the conditions for rolling back. After the switch, we check the agreed purchase flow.
For example, a store copy created at the start of testing will not contain orders placed later. Moving that old database back at the end could lose those orders. Before switching, we therefore agree how to include changes made during testing and when sales may need to be temporarily restricted.
We choose the target version after checking compatibility with the environment and add-ons. The cost and scope also depend on which modules can stay and which need adapting or replacing.
Product and category URLs after changes
Before a rebuild, we inventory product, category and important content URLs. We retain them where they still refer to the same material. If a URL must change, we plan a permanent redirect to its equivalent and update the store's internal links.
Acceptance checks also cover visits through old links, images and basic metadata. This lets us assess the effects on shoppers and search engines alongside the store's functionality.
A single repair or ongoing care?
You can commission a single diagnosis, repair or change. We agree regular help through our application and store maintenance service, with defined scope, hours and reporting channels. Larger upgrades and new features have their own scope and quote.
What should you send for a PrestaShop quote?
Send the store URL, describe the symptom or change you need, and explain its effect on sales or your team's work. Mention recent changes. If you know the PrestaShop version and important modules or integrations, include them; otherwise, describe what you can see.
We will use this to agree the next step and what needs investigating. If you are planning a new online sales operation, see our online store and catalogue development service.
Describe your PrestaShop issue or planned change
Send the store URL and describe the action that fails or needs changing. Explain its effect on customers or your team’s work.
Include the store version if known, recent changes and important modules or integrations. We will agree how to arrange any necessary access separately.