Skip to main content
GullySystem

Ecommerce Customisation Services

Ecommerce customisation is ongoing change to a store you already run, such as an added field, a changed rule or a rebuilt page. Changes are scoped in small pieces and released without stopping trading.

Handling a list of small changes

Most owners keep a list of small items. Each is too small for a project, and some cost money every week. The list is worked through in a fixed way.

Sorted by cost to you

A change that loses orders goes before a change that irritates a manager. Impact on orders sets the sequence, and each item is priced before it is started.

Grouped into releases

Several changes are tested and released together, which involves fewer deployments than releasing each item alone.

Written before it is built

One paragraph states what should happen and is agreed first. Much rework starts from a requirement that was never written down.

Four kinds of change

These differ in effort and risk. Knowing which one you are asking for helps with scoping.

Design

Layout, banners, category pages and product page arrangement. Visible, and low in risk.

Feature

A new field, rule or report. It needs a decision about what should happen in the unusual cases, such as a partial refund or an order with two addresses.

Workflow

A change to how an order moves through your team. It affects people and training as well as software.

Integration

Another system is joined on. It usually takes the longest, because the other side has its own rules and timings.

Changing a store that is trading

A live store has customers in the middle of checkout at any hour.

A copy to test on

Every change goes on a staging copy with real catalogue data before it reaches buyers. Staging is not skipped for small edits.

Released at a quiet hour

Deployments are made in the early morning, with the previous version ready to restore.

Watched afterwards

Error rate and order count are checked for the following day, because some problems show only in ordinary traffic.

FAQ

Frequently asked questions

Can you customise a store your team did not build?

Yes, after reading the code and the plugin list. Sometimes the first finding is that two old add-ons conflict, and removing one matters more than the change you asked for.

How are small changes charged?

Either as a small piece of scoped work or under a monthly arrangement for stores we look after. Effort depends on what is already in the store, so each piece is estimated before work starts.

Will customisation block our platform updates?

Not if it is built as an extension and not as an edit to core files. Child themes, hooks and separate modules keep your changes apart from the vendor’s, and updates are tested on a copy.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements