For arlanix/product-feed 1.0
Install
Magento 2.4.7 or later, PHP 8.1 or later and a working cron: the requirements are on the overview. Everything after the installation is done in the admin, by the store; the manual is theirs.
1. Get access to the package
Arlanix Product Feed is sold on Adobe Commerce Marketplace and installed from repo.magento.com, like any Marketplace extension. Composer needs the access keys of the Marketplace account that bought it: in Marketplace, My Profile → Access Keys, the public key as the username and the private key as the password. On an installation that already has Marketplace extensions they are in auth.json and nothing changes; otherwise:
composer config --auth http-basic.repo.magento.com <public key> <private key>
If the store owner bought the extension, ask them for the keys of their account, or for access to it: keys of an account that has not bought it do not see the package.
2. Add the packages
In the Magento root:
composer require arlanix/product-feed
arlanix/product-feed is a metapackage: it installs every Arlanix feed package at matching versions.
A store that needs only some of them can require those packages instead: arlanix/module-feed is the base, the others add a channel or a capability to it.
3. Upgrade the installation
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush
In developer mode the setup:di:compile and setup:static-content:deploy lines can be left out.
A store without Multi Source Inventory
Many single-warehouse stores have the Magento_Inventory* modules disabled. That needs nothing special: Arlanix_FeedInventory notices it, feeds count stock the single-source way, and the Inventory sources field stays out of the feed form. It also shows a system message at the top of the admin:
Arlanix Feed Inventory is installed, but Multi Source Inventory is switched off (…). Feeds count stock the single-source way and the "Inventory sources" field is hidden.
The message is information, not an error. To remove it, disable the module; nothing else changes:
bin/magento module:disable Arlanix_FeedInventory
bin/magento setup:upgrade
Do it before you hand the store back, or tell the owner the message is expected: it is the first thing they will see in the admin.
4. Check that the cron runs
The modules add their jobs to the Magento cron, most of them in a group of their own, arlanix_feed. An installation whose cron already works needs no extra setup. Cron and command line lists the jobs and how to check them; the short version:
bin/magento cron:run
bin/magento cron:install # only if cron:run says no crontab is installed
5. Confirm it works
Before you hand over, make one feed and run it; it takes two minutes:
- In the admin, Arlanix → Feeds → Add Feed. Identifier
install-check, Type Google Shopping, leave the rest. In Mapping, choose Google Shopping under Copy from and press Copy. Save. - In the grid, Select → Generate now on that row.
- Within two minutes the row's Last delivery shows a time and File a link. If it still says never delivered, the cron does not run the
arlanix_feedgroup: see Cron and command line. - Delete the feed, or leave it for the owner to edit.
Then tell the store owner it is done: the Arlanix menu is at the bottom of the admin's left-hand menu, and a test feed was generated.
If the menu is missing, the modules are not enabled. bin/magento module:status | grep Arlanix lists them; enable the disabled ones and upgrade again:
bin/magento module:enable Arlanix_Core Arlanix_Feed Arlanix_FeedTypes Arlanix_FeedGoogleMerchant Arlanix_FeedSftp Arlanix_FeedInventory
bin/magento setup:upgrade
What it adds to the store
Nothing on the storefront: the modules have no frontend code, layout or theme files. In the back end they add:
- the Arlanix admin menu, and Stores → Configuration → Arlanix;
- database tables named
arlanix_feed_*andarlanix_gmc_*; - three indexers, Arlanix Feed Products, Arlanix Feed Categories and, from
Arlanix_FeedInventory, Arlanix Feed Inventory Sources, which follow catalogue changes so a feed rebuilds only what changed; - cron jobs, in the
defaultgroup and in their ownarlanix_feedgroup; - the published feed files, under
pub/media/arlanix/feeds/; - their log,
var/log/arlanix.log.