Libraries tagged by Order Status

Simple Magento 2.4.7 patch for ACP2E-3130

Go to Download

Detects Magento order status transitions reliably and dispatches a single canonical event other modules can consume.

Go to Download

Send any email template to the customer when an order reaches a chosen status. Rules are managed in the admin, scoped per website or store view, with a subject and template per rule.

Go to Download

Records every Magento order status change: what it was, what it became, who changed it, from where, when, and from which IP address.

Go to Download

by this module you can add order status to each admin

Go to Download

WooCommerce comprehensive helper for custom order statuses.

Go to Download

The module ModMage_ChangeStatusOrder for Magento 2

Go to Download

Order Tags/Status for Flamarkt.

Go to Download

To ensure that we will not miss any sale and to keep track of the statuses of the orders a basic notification service needs to be created.

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download

A fraud detection tool for e-commerce platforms to analyze customer order behavior across Steadfast and Pathao couriers.

Go to Download

ReveChat Integration for Magento 2 - Seamlessly integrate ReveChat live chat widget into your Magento store

Go to Download

Configurable order lifecycle state machine for Laravel with guards, history, and events

Go to Download

A fraud detection tool for e-commerce platforms to analyze customer order behavior across Steadfast and Pathao couriers.

Go to Download

Configurable order lifecycle state machine for Laravel with guards, history, and events

Go to Download