Agricom

A farm shop theme that expects to sell in more than one language

The vendor's own headline for Agricom reads "RTL – LTR," and the description separately notes that RTL language support was added. Read with the compatibility list, that is the clearest picture of who the theme was built for: a grocery, vegetable store or agritourism business whose buying audience may read right-to-left. WPML appears among the compatible plugins, and the theme ships with a .POT file in its language folder for translating the text strings.

For a multilingual storefront, that combination does more work than a colour picker. WPML handles the content side; the RTL claim concerns how the layout mirrors. Both are vendor statements and worth confirming against your own translations before you commit, since a translated string can still break a carefully spaced hero.

The commerce side is unusually wide for a niche theme. The compatibility attribute lists WooCommerce 5.x.x through 9.x.x as separate entries — seven branches — and also names WP EasyCart and WP e-Commerce. Agricom's own description says it is "WooCommerce ready" and works with WooCommerce plugins. None of that was tested here; it is what the vendor declares. Multiple branches do suggest the author intends the theme to survive WordPress upgrades rather than pin you to one WooCommerce release.

Per-page settings, not one global template

Agricom's metabox layer is the part that changes a day of editing. The vendor says metabox plugins are integrated so you can make per-page definitions — unique menus and background images — and apply CSS to the header and footer areas for colours, spacing and height.

That matters on a site whose pages are not all the same kind of page. A campaign landing page for a harvest season, a wholesale enquiry page and a recipe blog post can each carry a different menu or a different header treatment without duplicating templates in the builder. The header and footer CSS controls are the vendor's stated route for one-off spacing adjustments when a page's content crowds the frame.

The same control panel is described as covering the preloader, the back-to-top control, logo, menu, colours, overall layout, footer, and sidebars on inner pages. It also claims editing of the 404, search and archive structures. That last point is easy to overlook: archive pages for a product category are exactly where a store's inventory sprawls, so having controls there is more useful than another homepage demo.

One-page scroll sections alongside a multi-page store

The vendor lists both one-page and multi-page layouts, and describes creating "onepage scroll sections for each page via metabox menu." Those two statements together describe something more flexible than a single scrolling site: individual pages can be given a scrolling section treatment while the rest of the site remains conventional.

A practical use is the front page of a farm business — an introduction, the produce, the farm's story, a contact block — built as one continuous scroll, while the shop, blog and product pages keep their normal structure. Since the scroll sections are enabled through a metabox menu, the setting is decided page by page rather than site-wide.

Sections themselves are built in WPBakery, with visibility options for individual items and controls for colour and fonts. Parallax background images and video backgrounds are also listed for sections. If you plan a hero of a field or a greenhouse with moving footage behind the heading, that capability is stated, not demonstrated to you here.

What the WPBakery editing model means for you

Agricom is a shortcode theme. The vendor states pages are built from more than 40 WPBakery shortcodes with a grid control system, and that the same elements work in pages, posts and custom post types. Components such as the logo, menu and sidebar are built for the theme and can be hidden or removed in the options panel.

The marketplace attribute for Gutenberg Optimized reads No. That is an optimisation label describing where the author put effort, not proof the block editor is switched off — but it does tell you the theme's page layouts are designed to be assembled in WPBakery. If your team has standardised on the block editor, budget for learning a different surface, or check how a block-built page behaves before you commit.

The slider layer is Revolution Slider, which the vendor describes as usable anywhere with ready-made demo sliders. Typography runs through the options panel with Google Webfonts, and the vendor states you can upload custom font families. The package listing names PHP, CSS and JS files plus a PSD, so the source files are there if a developer needs to adjust something the panel does not expose.

What the package and version claims actually cover

The marketplace attributes recorded on 4 November 2026 describe a responsive layout with three columns, widget-ready areas, high-resolution assets and "Well Documented" status. The theme's WordPress range runs from 4.9.x up to 7.0.x, and browsers listed include IE11, Firefox, Safari, Opera, Chrome and Edge. The newer WordPress entries are the author's declaration of support, not a record of testing on those releases.

Updates are described as handled through an Envato API integration: a notification appears in the dashboard and the theme updates with one click. The vendor also says paid plugins such as WPBakery and Revolution Slider can be updated from its own server. Treat that as the author's stated method rather than something the package guarantees, and keep a backup before any plugin update on a live shop.

The demo site is the fastest way to judge whether the layouts suit your produce and photography, because a farm store lives or dies on how its images and product grids look once your own photos replace the samples.

Questions & answers