Skip to content
Hedou Bibi
English
Let's talk

WordPress Customization: What to Check Before a Quote

Published:

Published by: Hedou Bibi

Need changes to an existing WordPress site? Share what works, what needs to change and how you’ll test it, so your developer can assess the work.

Need changes to a WordPress site? Start by looking at what’s already there. A small-looking change can depend on a theme, several plugins, previous custom code and an external service. A review helps identify what can stay, what needs to change and which features could be affected.

You do not have to choose the implementation yourself. Give the developer a clear description of the problem and the result you need, then ask for the reasoning behind the proposed approach.

Explain what the visitor needs to do

“Add product filtering” leaves several decisions open. Which attributes are used? Can conditions be combined? How are results sorted? What happens when nothing matches? Where will editors manage the data, and who fills in missing values for existing products?

For a fault, record the affected page, device, steps, expected result and actual result. A screenshot without customer data can help. That gives the team a way to distinguish a display issue from email delivery or a change in business rules.

Prepare four kinds of information

Scroll horizontally or use the arrow keys to view the full table.

Information What it helps establish
Site and environment The existing URL and known WordPress and hosting details.
Theme, plugins and licences Where features come from, previous changes and who controls renewals.
How the site works now User flows to keep working, known faults and available development notes.
Testing and recovery Whether there is a staging copy, a usable backup and an agreed recovery owner.

Write “unknown” where information is missing. An initial discussion can use the public URL and requirements. If access becomes necessary, arrange an appropriate handover rather than putting passwords or service keys in a shared public brief.

Compare a repair, a replacement and a partial rebuild

Each can be reasonable. A focused extension may suit a well-understood site. Overlapping plugins or unsupported custom code may justify comparing a cleanup with replacing one component. A complete rebuild should come with an explanation of why the existing structure cannot meet the agreed need.

Ask the proposal to identify what stays, what changes and what remains uncertain. A promise to support every old plugin is not a substitute for checking the actual dependencies.

Make it clear what the quote includes

  • Pages, data fields and journeys included in the change.
  • Existing features to preserve and historical issues excluded.
  • Responsibility for content cleanup, data entry and integrations.
  • Required licences, documentation and test access.
  • Environments covered by compatibility checks.
  • Release, rollback and support arrangements.

If important details are still unclear, agree on an investigation before committing to development. Agree on the output of the assessment, then quote the development against what it establishes. This makes unresolved work visible rather than hiding it inside an apparently simple fixed price.

Protect changes made while staging is in use

Your live site may receive enquiries, orders or new articles during development. Copying an older staging database over production can remove that newer information. Agree on whether the release moves code, changes fields or migrates selected data, and how the final comparison is made.

Recovery preparation should cover both website files and the database where appropriate. A copy of the theme alone is not a complete site backup. The person responsible for release needs a recovery procedure suitable for the actual environment.

Test the original request, then the existing user flows

For the filtering example, add a product, set its attributes, combine filters, clear them and open the detail on a phone. Check the agreed existing flows too. Record the results and remaining issues rather than accepting “uploaded” as the final check.

For earlier planning, use the custom WordPress quote checklist. Ongoing updates and fault handling belong in a separate WordPress maintenance scope unless the proposal explicitly includes them.

Need help with your website?

We’re Hedou Bibi, a WordPress team in Shanghai, China, operated by 上海禾斗匕匕网络科技有限公司. We work on WordPress customization, redesigns and new builds. Send your website URL and the changes you need to 1500351892@qq.com, or get to know our team.

Sources