Modernize Studio
Language: English
Email us

Connect

Integrations and APIs that keep your systems in step

When two systems do not talk to each other, someone copies data between them by hand, and the copies drift apart. We connect your applications through REST APIs, webhooks or scheduled file exchanges, and we build APIs so that others can connect to your software.

Before writing code we agree on the essentials: which system owns each piece of data, how a customer or a product is identified on both sides, and what should happen when one side is unavailable. Most integration problems come from leaving these questions open.

Every exchange we build is logged. When a call fails, it is retried if that is safe, and if it still fails, someone is told. You can see at any time what was sent, when, and with what result.

What it can look like

Online shop

New orderW-48212 items · €248.40

Management software

SO-10488Created from the shop
SO-10487Palmer & Rhee
SO-10486Studio Kerr
POST /api/orders → 201 Created · 142 msPUT /api/stock/EL-20431 → 200 OK · 38 ms · Stock sent back to the shop
Waiting for the next order
Illustrative example, fictional data

A new order from an online shop sent to the management software. Press the button to send it.

What we deliver

  • Connections between your systems

    Management software, online shop, CRM, accounting, warehouse and shipping, connected so that data is entered once.

  • APIs for your application

    Documented REST APIs that let partners, apps or your own tools read and write data securely.

  • Webhooks and file exchanges

    Real-time notifications where the systems support them, scheduled CSV, XML or JSON exchanges where they do not.

  • Logging and alerts

    A record of every exchange, automatic retries and an alert when something needs attention.

  • Documentation

    What each integration does, how to monitor it and how to change it.

Typical projects

  • Online shop and management software

    Orders from the shop created in the management software, stock levels sent back to the shop every few minutes.

  • CRM and accounting

    Customers created in the CRM appear in the accounting package, and invoices flow back to the customer record.

  • Shipping labels

    Shipments booked with the carrier from the order screen, with the tracking number stored on the order.

Technologies

  • REST APIs
  • Webhooks
  • OpenAPI
  • OAuth 2.0
  • JSON, XML, CSV
  • C# / .NET
  • PHP
  • SQL Server
  • MySQL

How we work

  1. Map the systems

    We list the systems involved, which one owns each piece of data, how records are matched and what happens when one side is unavailable.

  2. Proposal with a fixed price

    We reply in writing with the approach (API, webhook, database or file exchange), the stages and a fixed price.

  3. Trial run on a copy

    The integration, automation or migration runs first against test data, and you check the result before anything touches live data.

  4. Go-live with monitoring

    Every exchange is logged, failures are retried when that is safe and reported when they are not. You receive the documentation.

Price and payment

Payment terms

We ask for 50% to start and 50% on acceptance. The second half is due before go-live and before the source code is handed over. Larger projects are split into milestone payments.

Every proposal states a fixed price for the work it describes, agreed in writing before work starts. If the scope changes, we send a new written quote and wait for your approval before doing the extra work.

Prices exclude VAT.

Prepare a project brief

Questions about this service

What if one of our systems has no API?

There is usually another way: a database the system writes to, an export it can produce on a schedule or a file it can import. The proposal states which route we will take.

Who pays for outside services?

Fees for outside services, such as a carrier's or a payment provider's API, are paid by you directly to the provider. Our proposal covers the integration work.

What happens when an exchange fails?

The failure is logged, retried when that is safe and reported. Nothing is dropped silently.

Can you document an API for our partners?

Yes. We publish an OpenAPI description together with a short guide and examples.

Contact

Use whichever channel suits you. We reply within one working day, in writing.

By email

riccardo@modernizestudio.com
Write an email

List the systems involved and what should flow between them. We reply within one working day.

Send us your file

For Access, Excel, VB6, Delphi or older .NET software, you receive a free written assessment within 48 hours of sending the file.

  1. Make a copy, with test data if you prefer.
  2. Attach it to the form or to an email, ideally as a password-protected archive with the password sent separately. If you ask, we sign an NDA first.
  3. Within 48 hours: the assessment and a fixed price for a pilot module.

We work from Italy.

Send a message

Optional. A database, a workbook, screenshots or a specification, up to 10 MB. For larger files, put a download link in the message.

Email us

The button opens your email program with the message ready. Nothing is sent until you press send there.

Email us