How Ari works

How a change gets made on your Magento store

Describe the change in a chat. Ari builds it, you check it, and your developer releases it.

Three steps in every change

Show a delivery date under the Add to cart button on every product pagehartwell-chocolatier.com · Preview store

You ask for the change

Write it in the chat, in any language.

preview.hartwell-chocolatier.com/autumn-harvest-tinThe Hartwell product page with the new delivery date under Add to cart

Ari builds it on a copy

You check it on the preview store.

Human reviewChecks passed18 testsApproved byTomMerged intomainReleased15:02

A person releases it

Your developer, your agency or Ari engineers.

Ari is trained on

The largest Magento knowledge base in the world

hours of Magento developmentMagento tickets, each one solved

One change, from request to live store

14:32Marta, eCommerce manager

Marta asks for the change, and Ari checks one detail

If a request could mean two things, Ari asks first. Here it checked the 2 pm dispatch cut-off, because without it the date would be wrong every afternoon.

AriPreview storeK
show a delivery date under the Add to cart button on every product page

Your warehouse ships the same day for orders placed before 2 pm. Should the date use that cut-off and skip weekends and holidays?

yes, and use the postal code from the customer’s account when there is one

14:34Ari

Ari reads the store before it writes anything

Ari starts from the code your store actually runs, including the custom modules a previous developer wrote, and from the settings in your admin.

  • The template in your theme that holds the Add to cart row
  • The shipping origin and carrier transit times
  • The tests that already cover the product page
What Ari read before writing a line52 s
Magento_Catalog/.../addtocart.phtmlThe Add to cart row, in your theme
Stores › Shipping › OriginOne warehouse, in British Columbia
Carriers › transit timesTwo to five business days, by province
customer_address_entityA postal code on most accounts
app/code11 custom modules, none on the product page
dev/tests18 product page tests, all passing
14:39Marta checks the result

Marta opens the changed page in the preview store

The preview store is a working copy of your storefront and admin. Marta clicks through it like the real store. If the date sits in the wrong place, she says so in the chat and Ari moves it.

Preview store · hartwell-chocolatier.com/autumn-harvest-tin
The product page before the change The product page after the change, with the delivery date BeforeAfter
14:41Ari

Ari opens a pull request in its copy of your repository

The change is ordinary Magento code in your theme and a small module, written the way your developers write it. The tests Ari added run next to the ones you already have.

ari/hartwell-magento/pull/2142 files
OpenShow a delivery date under Add to cart
Magento_Catalog/templates/product/view/addtocart.phtml
<?= $block->getChildHtml('addtocart.button') ?></div>+ <?php if ($date = $deliveryDate->forProduct($_product)): ?>+ <div class="hw-delivery-date">+ <?= __('Arrives %1 to %2', $date->label(), $date->postcode()) ?>+ </div>+ <?php endif; ?>
Product page tests, 18 passedNew tests for the 2 pm cut-off, 6 passedStatic analysis, clean
14:46Tom, developer

Tom reviews it like any other branch

He reads the code and approves it. If he wants something done differently, he asks Ari in the same chat.

Review · pull request #214
Tom commented on line 3

Can the 2 pm cut-off come from the admin instead of the code? The warehouse changes it before holidays.

Ari in the chat

Moved it to Stores › Configuration › Sales › Delivery date. The default stays 2 pm.

Tom approved these changesApproved
15:02Tom releases it

It goes live through your own release process

Tom merges it into your repository and the store's usual pipeline deploys it, on your servers and on your schedule. Marta sees the change marked live in the chat.

Deploy · productionmerged by Tom
composer install38 ssetup:upgrade21 ssetup:static-content:deploy en_US fr_CA2 min 40 scache:flush3 sLive on hartwell-chocolatier.com15:02
Ari to Marta

The delivery date is live on hartwell-chocolatier.com. Tom merged it at 15:02.

Ari makes a copy of any repository

We clone your repository once, and Ari works on that copy. A person reviews each change and merges it into your repository, where your usual checks and release run.

GitHub, GitLab, Bitbucket and Azure DevOps

What you need to get started

1

Access to your repository

Read access to the code, with its history. We clone it once, and Ari works on that copy.

2

Composer credentials

The keys for Adobe's repository and for the paid extensions you run, so the preview store runs exactly the versions you have.

3

A sanitized database dump

Your catalog, settings and CMS content, with customer data removed before you send it.

Then a short call with an Ari engineer. They set up the preview store with your developer, check that it matches your live store, and add your team.

Connect your store

Pricing

A month of Ari for less than 2 developer hours

$99from, per month

Connect your storeContact us

Enterprise plans carry custom volumes and terms. Contact sales, or read what it costs and how it works.