Four ways to customise Orbit, with no forks

A coffee brand and a desk brand should not have the same store. On a template, they usually do. Kugie Orbit is built to be customised.

The problem with forks

The usual way to customise a store is to copy the code and change it. That copy is a fork. A fork stops getting the engine's updates, and every fix has to be done twice.

Orbit never forks. Every brand runs the same engine. What makes your store yours sits in four places that the engine is designed to call.

The four extension points

1. Hooks. Change how a step works. For example, how a price is worked out for a reseller.
2. Events. React when something happens. For example, send a message when an order ships.
3. Client modules. Add something new that only your brand needs.
4. Runtime settings. Switch behaviour on or off without new code.

What you get

Your store looks and works like your brand. And it keeps getting every update to the engine, because nothing was forked.

How changes are made

You ask for a change. Kugie builds it as a bespoke ticket, through these extension points, with a two-week turnaround. Pricing.

Next steps

• See the product page: Orbit.
• See the prices: pricing.
• Ready to talk about your store? Start the assessment. It opens with Orbit selected.