Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Take over, repair and look after an online store built on custom code

Some online stores run on code written for that one business, usually PHP with a MySQL database, rather than on a store platform such as WooCommerce or Shopify. When the developer who wrote it is no longer involved, we find out whether the code you hold can run the store without them, test how orders go through and fix what stops customers from buying. The code, hosting and accounts remain yours, and anything the previous developer still holds is moved into your name.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml takes responsibility for the code your store runs on: we review and document it, fix checkout, payment and order problems, and keep PHP and the framework on supported versions. Each change is tested on a working copy before customers see it.

What we take on in a store built on custom code

Work starts with the first two parts below, which show what the code needs and where buying breaks. The others are agreed afterwards, in the order the findings suggest.

Solution
Websites
  • A check that your copy of the code is completeWe confirm the framework, its version and the PHP version the store needs, then list everything the code depends on: configuration, database tables, outside libraries, scheduled tasks and files kept only on the server. That list is checked against both the live server and a working copy of the store.
    01
  • Test orders through checkout and fulfillmentOn the working copy, with payments in test mode and customer emails switched off, test orders go through each kind of product, every shipping method and each payment option. We compare shipping and tax totals with your rules, check the order emails and follow each order into the admin and any fulfillment or print-on-demand service the store sends orders to.
    02
  • Fixes for checkout, payment and order problemsFailed payments, wrong totals, orders that never reach the admin or the fulfillment service, missing order emails and pages that return errors are reproduced on the working copy and traced through the code and the server's error logs. Payment and shipping connections built on retired versions of a provider's API are moved onto current ones. Each fix is logged with how it was tested.
    03
  • Security, PHP and framework updatesWe review admin accounts, how the code handles form input and file uploads, configuration files the web server could expose, and whether card details go straight to the payment provider rather than through the store. Old framework and PHP versions stop receiving security fixes, so upgrades are planned in steps and tested on the working copy before the live store changes.
    04
  • The code in Git, with a written setup recordThe code goes into a Git repository in your account, and every later change is recorded there. The setup record explains how to install and deploy the store, where its configuration lives, which outside services it calls and which scheduled tasks it needs, and names who holds each account, so another developer could continue the work.
    05
  • A move to hosting in your nameIf the store runs on a server the previous developer controls, we copy the code, database, uploaded files, scheduled tasks and email settings to hosting in your account and test the store on a temporary address. At an agreed time, new orders pause while the final database copy is made, and the domain is pointed at the new server.
    06
  • A later move to a store platform, if you want oneIf the review shows the code is not worth keeping, or you would rather run WooCommerce or Shopify, we plan the move as separate work: products, customers and orders mapped to the new platform, the features your store relies on compared with what the platform offers, and redirects for every changed address. The current store keeps selling until you approve the switch.
    07
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need to take on your store's code

  • The code and anything left with itThe copy of the code you received, as an archive or a repository, plus any notes, instructions or change history from the previous developer.
    01
  • A database exportA recent export of the store's database, or access to the hosting account so we can make one.
    02
  • Hosting access in each person's nameNamed accounts for each member of our team on the hosting control panel and the server, so you can remove any of them at any time. If someone else holds the hosting, tell us who.
    03
  • Test access for payments, shipping and fulfillmentSandbox or test-mode keys for the payment provider, and access to the shipping and fulfillment services that receive the store's orders.
    04
  • How your totals should add upHow shipping costs, taxes, discounts and refunds are meant to work, so test totals are compared with your rules and not with what the code happens to do.
    05
  • Problems you already seeOrder numbers, error messages or screenshots for problems that customers or staff have reported.
    06
  • Who decides on repairs and release timesA named person who decides which repairs go ahead and agrees release times outside the store's busiest hours.
    07

How a takeover runs

  1. [Access and an account list]

    We set up named access, then list every account the store depends on, such as hosting, the domain, the payment provider, shipping and fulfillment services and email sending, with the person who holds each one.

    Step 01
  2. [A working copy]

    The store is set up on a separate server using your code and a database export. Nothing on the live store changes during the review.

    Step 02
  3. [Review and test orders]

    We read the code, run the test orders and check security and performance. Where the live store and the working copy behave differently, we compare them to find out why.

    Step 03
  4. [Findings you decide on]

    A written report ranks the problems by their effect on buying and on security. You choose which repairs we make and in what order.

    Step 04
  5. [Repairs and releases]

    Each repair is made on the working copy and tested with orders before release. Releases go out at agreed times after a fresh backup, and the next live orders, payments and emails are checked as they come in.

    Step 05
  6. [Ongoing care or a handover]

    The store can stay with us for updates and fixes. Otherwise the work ends with the repository, the setup record and every account in your hands, and our access is removed.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions owners ask before a code takeover

Do we have to rebuild the store?
No. The work starts with the code you have and keeps it running. A rebuild or a move to a store platform comes up only when the findings show that keeping the code would take more work than replacing it, or when you ask for it.
How do you know whether our copy of the code is complete?
By running it. If the working copy will not start, or a page or feature fails, the errors show what is missing. Missing parts can come from the live server or the previous developer, and lost configuration can be recreated. Anything that cannot be recovered is listed with what rebuilding it involves.
Can you start without access to the live server?
Partly. Reviewing the code and running it on a working copy needs only the code and a database export. Comparing that copy with the live store, and releasing any fix, needs access to the hosting.
Which stores is this work for?
Stores whose code was written for the business, usually in PHP with a MySQL database, either on a framework such as CodeIgniter or without one. A store on WooCommerce or Shopify follows that platform's own update routine instead.
What access do you need to our payment provider?
For testing, only its sandbox or test-mode keys. Live test orders happen only if you authorize them, and then we also need permission to see and refund those payments. Payouts and bank details stay in your hands.
Who owns the code and the accounts?
You do. The repository, hosting, domain and service accounts stay in your name, or are moved into it, and we work through access you grant. Every change we make goes into your repository.
Our host is retiring the PHP version the store uses. What happens?
We check whether the store's framework version supports a newer PHP release. If it does, the working copy runs the new version, and code that fails there is fixed before the live server switches. If the framework itself needs a new major version, the upgrade can touch much of the code, so it is scoped and tested as its own piece of work.
Will we know what the repairs involve before agreeing to them?
Yes. The review is a separate first step and does not commit you to any repairs. Each finding describes the problem, what fixing it involves and how the fix will be checked, and each repair gets a written scope for your approval before it starts.
Do we need an ongoing plan?
No. The review and repairs can be a one-off project. If you want ongoing care, such as updates, security fixes and checks after each release, we agree what it covers before it starts, either monthly or task by task.
Does this include a redesign, SEO or new features?
No. A redesign, new features, SEO and advertising, adding products or content, and a move to a store platform are scoped separately. Legal and tax decisions stay with you and your advisors. Hosting, domain and service fees are not included unless the agreement names them.

Read these store and site projects in full

See where each of these clients started and what we delivered, before you choose who looks after your store's code.

See all case studies