NL EN

Custom Magento modules, including our own.

When your shop needs something no existing module does well, we build it. Properly, so the next upgrade is not a project.

Tell us what you need
Drawing of a custom module above Magento, hooking in at four fixed connection points: an observer, a plugin, an admin screen and an API. Magento itself stays untouched.ObserverPluginAdmin screenAPIYour moduleMagento itself stays untouched

Where an upgrade breaks, it is usually custom code.

Not Magento itself, but code that was once put into the core in a hurry, or a module that overrides more than it needs to. Then every update is a gamble, and the shop falls behind.

We build modules to survive an upgrade. That takes a little more care while building, and saves time on every update after that.

How we build.

Never in the core
We do not change Magento itself. A module hooks in at the places Magento provides for that: plugins, observers, its own admin screens and API routes. That way an upgrade stays an upgrade.
Configurable in the admin
Whatever can differ per store or situation goes under Stores and Configuration. You do not have to email us for every threshold or piece of text.
Permissions per role
A module’s admin screen gets its own permissions, so you decide who can see it and who can use it.
Database the Magento way
We define our own tables in Magento’s declarative schema. Installing and updating then needs no manual work in the database.
Tested and in Git
The code lives in Git and is installed with Composer. Every version goes to staging first, and we test the steps that matter: ordering, paying, shipping.
Documented
Every module comes with a short description of what it does, which settings it has and where it hooks in. The next developer does not have to guess, even if that is someone other than us.

What we build

  • Price rules or terms for business customers that standard Magento cannot handle
  • Extra fields and checks in the checkout
  • An admin screen that brings together information you now collect from three screens
  • Import and export of products, prices or stock in your supplier’s format
  • Shipping rules per product, weight or size, such as a surcharge for long parcels
  • An integration with a system that has no ready-made module
Drawing of our warehouse module: a cart with crates, one per order, a tablet with the packing slip and a handheld scanner scanning a product into a crate.Packing slip on the tabletEvery product scannedOne crate per order
In development

Our warehouse module.

Order picking with a handheld scanner on a tablet, directly in Magento. No paper packing slips, no separate warehouse system that needs integrating as well.

Picking
The picker asks the tablet for the next order and gets the first one nobody has taken yet. Every product is scanned, by EAN or SKU. Three items means three scans. A wrong product or one too many shows on the tablet straight away.
Packing and completing
At the packing table everything is scanned once more. If the order is right, the module completes it in Magento: invoice and shipment in one go, after which your shipping integration can create the label.
Overview
The warehouse manager sees what is in progress, can give orders priority or put them back in the queue, and sees what each person did per day: in orders, in lines and in items. That way three large orders do not count as less work than seven small ones.
Configurable
Working with order cards or without, how many orders fit on a cart, which products do not need scanning. It lives in Magento’s configuration, not in the code.
Scanning
An ordinary handheld scanner that acts as a keyboard, on a tablet with a browser. The tablet’s camera works too, as a backup.

Want to see it, or have a warehouse where you would like to try it? Email us.

Questions

What does it cost to have a Magento module built?

That depends on what the module has to do, so you get a proposal up front: a fixed price for the job, or an hourly basis if the scope cannot be pinned down in advance. We start with a short description of what the module should and should not do, which you can add to. Building only starts once that is right. A first conversation about your idea costs nothing.

Does a custom module still work after a Magento update?

That is what we build it for. Because we do not change Magento itself and only hook in where Magento allows it, a module survives most updates without changes. For a major upgrade we test it on staging as part of the upgrade, and if something needs to change, you see that before the upgrade goes live.

Who owns the code of a custom module?

You do. The code of a module we build specifically for you goes into a repository of yours, so you can take it with you or have someone else maintain it. If you would rather not manage that repository yourself, we host it for you in a Forgejo environment of your own. For our own modules, such as the warehouse module, we make separate agreements.

Can you change or replace an existing third-party module?

Yes. That is often the first step: we go through the modules in your shop and look at which ones are unused, which slow the shop down and which hold back an upgrade. We prefer to change a third-party module through an extension of our own, so an update from the vendor does not wipe out your change.

When will the warehouse module be available?

It is in development and runs in a test environment. We do not give a date; it is ready when it is right. If you want to see it, or have a warehouse where you would like to try it, email us. Then we show you what it can do today.

From the knowledge base

More about Magento

Tell us what you run.

An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.

Get in touch

or email [email protected]