kingfisher systems
Menu

Shopify · integrations · custom software · AI

Your store, your systems and your team, in step

Shopify development, system integrations, custom software and practical AI for retail and ecommerce brands that want the online store, the warehouse, the wholesale portal and the accounts to tell the same story.

Bring the thing that is slowing you down: a page that loses customers, an order that has to be typed twice, a job that lives in a spreadsheet. We will work out the next step together, and you deal with us the whole way through.

Discuss your projectExplore the work

Direct, start to finish. You work with Chris through the brief, the build, the review and the handover, and he is still there after launch.

The whole picture, not just the page. Customer experience, business rules and the systems underneath, including the connections between them, because that is where most ecommerce problems actually live.

01 / Shopify development

A store that sells well and stays easy to run

We improve the themes you already have, build the features they are missing and stage every change on an unpublished theme, so you see it before your customers do and nothing goes live until you say so.

Explore Shopify development

SEE THE WORK

2XU: Theme architecture and performance2XU: Apparel21 integration

What the work can include

Shopping journeys

Finding a product, comparing two, picking a size, checking out, on a phone in a hurry as much as on a desktop.

Theme engineering

Architecture, performance, reusable sections your team can use for the next campaign, and how third party apps fit in without weighing the store down.

Releases you control

An unpublished preview, the affected journeys checked, and publication as your call, not ours.

02 / System integrations

Orders, stock and fulfilment that agree with each other

We connect Shopify to the warehouse, the wholesale portal, the point of sale and the accounts, with the rules for which system owns what agreed in writing, so nobody types the same order twice and the storefront works from the stock the warehouse holds.

Explore System integrations

SEE THE WORK

ELK: Connected retail operationsBicycle Superstore: Fulfilment integration

What the work can include

What moves

Products, orders, stock, shipments and the identifiers that tie them together, between Shopify and systems such as Cin7, Datapel, Apparel21, Retail Express, NuORDER, ShipStation and Starshipit.

What goes wrong

Returns, exchanges, duplicate events, missing fields and the records a person needs to look at, handled on purpose rather than discovered by a customer.

How you would know

Run summaries, reconciliation, staged rollout and a way to recover when something does not land.

03 / Custom software

A tool built around the job, not the other way round

Some work crosses several systems or follows rules no off the shelf app understands. We turn that process into a focused application with the information, permissions and review steps your team needs, and nothing they do not.

Explore Custom software

SEE THE WORK

MSS Repairs: Repair operations

What the work can include

Kinds of tool

Internal applications, specialist ordering flows, job and repair management, operational dashboards.

Built in controls

Clear inputs, real validation, visible progress and care around anything that changes a business record.

Ready to run

A tested first version, hosting agreed, and the guidance your team needs to operate and maintain it.

04 / AI integrations

An assistant that answers from your records, not from guesswork

We connect Claude, ChatGPT and other assistants to your business information for specific tasks, read only by default, with a person reviewing the result before anything is acted on.

Explore AI integrations

What the work can include

Typical tasks

A stock or product lookup, an internal briefing, a draft reply prepared from known records.

Access

Selected tools over authenticated connections, with explicit limits on what an assistant can read or change.

Testing

Representative prompts, missing information, partial results, and the actual assistant your team plans to use.

05 / Storefront performance

Faster pages, same design

We measure what is slow on the pages customers use, fix it in the theme and the third party code around it, and report preview and field results separately.

Explore Storefront performance

SEE THE WORK

2XU: Theme architecture and performance

What the work can include

What we measure

Largest Contentful Paint, Interaction to Next Paint and layout shift on mobile and desktop, in the lab before release and in the Chrome UX Report after.

What we change

The build, asset delivery, loading order, image priority and the schedule third party scripts run on, within your existing theme.

What you get

A baseline, a preview you can test, and a report that says what moved and what did not.

06 / Accessibility

WCAG 2.2 AA, checked in the states that matter

Automated and manual checks against WCAG 2.2 Level AA on storefronts and operational tools, the fixes made on a preview, and a statement that says what was tested.

Explore Accessibility

SEE THE WORK

2XU: Theme architecture and performance

What the work can include

What we check

Names, roles, focus order, contrast, target sizes and keyboard operation, on the page as it loads and inside menus, drawers, dialogs, search and size selection.

How we check

axe-core, IBM Equal Access, pa11y and the Nu Html Checker, then keyboard and screen reader passes by hand.

What you get

A ranked report against WCAG 2.2, the fixes in your theme, and a published statement.

Choose a useful starting point

Start small. Build from there

Most engagements start with a conversation about what happens today, then a short written scope and terms for a first piece of work, agreed before any code. You know what you are buying before you buy it. Any ongoing support is agreed as part of the scope.

01

One defined improvement

A customer journey, a feature or an operational problem with a clear goal. We look at what is there, agree the change with you and build something your team can review.

02

A new connection or application

Start with the workflow, the people using it and the systems involved. We build in stages and test the important assumptions early, so surprises arrive while they are still cheap to fix.

03

Ongoing development and care

For software that needs looking after: an agreed backlog, maintenance and monitoring, with priorities and response times set around what the work needs. We want what we build to keep working well for you long after launch.

From first conversation to everyday use

A clear process. Working progress you can see

You should always know what is being built, why the decisions were made and what has to happen before release. No big reveal at the end.

01

Understand the work

Walk through the current task, the people involved and the systems it touches. Agree what a good result looks like before choosing how to build it.

02

Set a scope you can hold

Deliverables, dependencies, access and review points, in writing. The first change is separated from the ideas that can follow it.

03

Build something you can review

Working progress shared as it happens, the relevant workflows tested and time made for your feedback. Release follows a separate agreement after you have reviewed the work.

04

Put it to work

Rollout agreed, receiving systems or customer journeys verified, operating steps written down. Maintenance and monitoring for the work that needs it.

The work in practice

Customer experience and operations, connected

Two projects that show the range: one on the storefront, one entirely behind it.

Before we start

Bring the problem. We can shape the brief

Do we need to write a technical brief?

No. Walk us through the current task: what happens, who uses the systems, where it hurts and what better would look like. We turn that into a technical scope together.

Can you work with an existing website, application or integration?

Yes. We read the current code, configuration and workflow before recommending anything. Sometimes that is a focused fix, sometimes an extra connection, sometimes a staged replacement. We will explain which approach fits and why.

Can you collaborate with our team or another agency?

Yes. We take responsibility for a defined part of the project and coordinate interfaces, access, review and release with the people already involved. Agreeing early who owns each part is what keeps the work moving.

How are cost and timing agreed?

We assess the requirements, dependencies and review points with you before quoting. Existing code quality, platform access, third party constraints and the size of the workflow all affect the scope and estimate, and you see the estimate before any work starts.

What happens after launch?

We agree the handover and who owns hosting, monitoring and maintenance. If the work needs ongoing development or support, that is scoped alongside the initial build rather than discovered afterwards.

Do you only work with Melbourne businesses?

No. Kingfisher Systems is in Melbourne and works remotely with teams elsewhere. We agree how we will communicate and review around the people involved.

Work directly with Chris

What needs to work better?

Tell us about the task, the systems involved and what you want to improve. A clear starting point is enough.

Discuss your project