Automation integration

Extend Ordering.co with your own plugins.

Add your own logic to Ordering.co without changing the platform. A plugin reacts to orders, carts, menus, businesses, deliveries, and payments, and it has its own settings in the Dashboard.

Plugins extend Ordering.co. Ordering.co runs the operation.

A plugin adds the logic that makes your business different. Ordering.co gives you everything around it:

  • Your own channels. Branded websites, apps, and kiosks where customers order from you directly.
  • More products and features. More than 20 products and more than 1,500 features across ordering, loyalty, marketplaces, call centers, and delivery.
  • Custom design. Our team helps you shape the experience your customers see.
  • Built to extend. Plugins, APIs and MCP, and application source code on eligible plans.

Why use Plugins with Ordering.co

  • Extend without forking. Your plugin runs as its own service, so your code stays separate from the platform.
  • React at the right moment. Hooks run when orders, carts, menus, businesses, deliveries, and payments change.
  • Change data, not only watch it. Filters return transformed data and prehooks can stop a request, so a plugin can shape how Ordering.co behaves.
  • Settings in the Dashboard. Each plugin gets its own settings, so operators configure it without touching code.
  • Proven in production. More than 40 of the integrations in our catalog run as plugins, including payment gateways, POS systems, delivery companies, and marketplaces.

What you can build

Plugins declare what they are in their manifest. The integrations in our catalog show the main kinds:

  • POS systems. Send each new order to the POS, keep order status in step, and sync menus and business details. Examples: Square, Clover, Oracle Simphony, Shopify.
  • Payment methods. Add a payment method and take and confirm each payment through the provider. Examples: HitPay, Redsys, Mercado Pago, Stripe Terminal.
  • Delivery companies. Quote deliveries at checkout, create the delivery when the order is placed, and cancel it when the order is canceled. Examples: Uber Direct, Shipday, Rappi Cargo, Yango Delivery.
  • Sales channels and middleware. Publish your menu to a marketplace and keep its orders in step. Examples: Uber Eats, Deliverect, Stream.
  • Your own business rules. Validate a request, enrich data, or keep an external system in step with your operation.

How a plugin works

1. The manifest

Every plugin publishes a config.json file at its root URL. It declares:

  • Identity: name, unique key, description, author, and version.
  • Hooks: the events the plugin listens to, the type of each hook, the path Ordering.co should call, and an optional delay.
  • Settings: the fields operators fill in, with translations for each language.
  • Payment methods: any payment method the plugin adds to Ordering.co.
  • Install and setup links: an address Ordering.co calls right after installation, and pages the plugin hosts for general settings and per-business setup.

2. Installation

When you add the plugin URL in the Dashboard, Ordering.co reads the manifest and:

  1. Registers the plugin and its hooks.
  2. Creates a Plugin settings section with the declared fields.
  3. Creates the payment methods the plugin declares.
  4. Calls the plugin’s install address with your project, so the plugin can connect back to the Ordering.co API with its own access.

Update reads the manifest again and applies new hooks and settings. Delete removes the plugin with its settings and payment methods.

3. Hooks

Ordering.co calls your plugin in three ways:

  • Actions run after an event, in the background, so they do not hold up the request that triggered them. Use them to send an order to a POS or create a delivery. An action can wait a set number of seconds before it runs.
  • Filters receive data and return it, changed or not, before Ordering.co uses it. Payment plugins use filters to take and confirm payments.
  • Prehooks run before Ordering.co processes a request. They can add data to the request or stop it with an error message.

Every call includes the event data, the request details, the user who made it, and the plugin’s settings.

4. Settings

Operators configure the plugin in Plugin settings, from the fields its manifest declares. A plugin can also open its own settings page inside the Dashboard. POS, sales channel, and delivery plugins connect business by business from the Connect section, so each store can use its own setup.

Hooks you can use

Ordering.co exposes more than 280 named hooks. These are the hooks Ordering.co’s own plugins use, grouped by area:

  • Orders: orders_register, orders_update, orders_delete, orders_reorder.
  • Menu and catalog: sync_menu, push_menu, products_update.
  • Businesses: sync_business, business_update, business_delete, business_configs_update, business_metafields_register, business_third_party_integrations_update, business_third_party_integrations_delete.
  • Cart and checkout: cart_add_product, cart_update_product, cart_remove_product, cart_multi_product, cart_change_paymethod, order_options_update.
  • Delivery: delivery_create_order, delivery_update_order_status, delivery_cancel_order, driver_company_register.
  • Payments: paymethod_<gateway>_pay, paymethod_<gateway>_confirm, paymethod_<gateway>_group_pay, paymethod_<gateway>_group_confirm, plus user_paymethod_paymethods_register, user_paymethod_paymethods_search, and user_paymethod_paymethods_delete for saved cards.
  • Customers and accounts: users_register, users_update, users_login, addresses_register, code_verification_<channel>_sent.
  • Project settings: configs_update.

Set up and go live

The Deliverect and Shipday guides show the same install flow:

  1. In the Ordering.co Dashboard, open Settings > Developers > Plugins.
  2. Select Add new plugin, enter the plugin URL, and add it. Plugins provided by Ordering.co can also be installed from the System Plugins list on the same screen when it is shown.
  3. Open Plugin settings, select the plugin, and fill in its settings.
  4. For POS, sales channel, and delivery plugins, connect each business from Connect.
  5. Test with the provider’s sandbox or a test business, then go live.

Use Enable to turn a plugin on or off, Update to load a new version of its manifest, and Delete to remove it.

More ways to extend Ordering.co

  • Webhooks send Ordering.co events to a URL you choose.
  • Ordering API lets your applications work with orders, businesses, categories, and products.
  • APIs and MCP connect your systems and compatible AI tools to Ordering.co.
  • Automation and more lists the other ways to connect and automate your operation.

How it works

Describe your plugin, install it, and let Ordering.co call it.

  1. 01
    Publish a manifest

    Your plugin is a web service with a config.json file that declares its name, key, version, hooks, settings, and any payment methods it adds.

  2. 02
    Install it from the Dashboard

    Add the plugin URL in Settings > Developers > Plugins. Ordering.co reads the manifest, registers the hooks, and creates the plugin's settings.

  3. 03
    React to hooks

    When an order, cart, menu, business, delivery, or payment event happens, Ordering.co calls your plugin with the data and your plugin settings.

Resources

Guides and references.

Questions

Frequently asked questions.

What is an Ordering.co plugin?

A plugin is a web service that Ordering.co calls at specific moments, such as when an order is placed, a cart changes, or a menu sync runs. It is described by a config.json manifest and installed from the Dashboard, with its own settings and its own list of hooks.

Do I need to change or fork Ordering.co to build a plugin?

No. Your plugin runs as its own service. Ordering.co reads its manifest, registers its hooks, and sends it the event data. You can enable, disable, update, or remove it from the Dashboard at any time.

How is a plugin different from a webhook?

A webhook sends an event to a URL you choose. A plugin goes further. It can change data before Ordering.co uses it, stop a request with its own error message, add payment methods, and bring its own settings screens into the Dashboard.

Can a plugin add a payment method?

Yes. A plugin can declare a payment method in its manifest. Ordering.co creates it when the plugin is installed and calls the plugin to take and confirm each payment. Most payment gateways in our catalog work this way.

Can a plugin block an action?

Yes, with a prehook. A prehook runs before Ordering.co processes a request and can add data to it or stop it with an error. For example, a plugin can keep an order that an administrator canceled from being changed again.

Where do plugin settings and credentials live?

Settings declared in the manifest appear in Plugin settings in the Dashboard and are sent to your plugin with every hook. A plugin can also open its own settings page inside the Dashboard. Keep credentials in those settings, never in the plugin code or in shared documents.

Who can build plugins?

Your own developers, an agency, or a software company. Ordering.co builds many of its own integrations as plugins, and our team can help you plan yours.

Why build on Ordering.co?

Plugins let you add your own logic. Ordering.co gives you the operation around it, with your own branded channels, more than 20 products and more than 1,500 features, custom design with help from our team, APIs and MCP, and application source code on eligible plans.

Build on Ordering.co without forking it.

Tell us what you want to connect or automate, and we will help you plan the plugin, the hooks it needs, and how to test it.