The menu is a post type, not a page section
The vendor's feature list describes a Restaurant Menu custom post type with several menu layouts. Each dish becomes an entry in the WordPress admin rather than a line of text inside a page, so a long menu stays a list you can edit and reorder instead of prose you rewrite.
Three shortcodes present that content differently: a Restaurant Menu List, a Restaurant Menu Gallery and a Restaurant Menu Carousel. A lunch list, a photo-led specials board and a scrolling bestsellers strip can all read from the same items, so changing a price happens once. The version 2.0 changelog from February 2023 added support for an "order" value on the post type, which is how you control which dish leads a section.
Two booking routes, and the difference matters
Piquant offers bookings two ways in the vendor's description: a Restaurant Reservation Form shortcode that places an enquiry form on your own site, and an OpenTable integration for venues already running bookings through OpenTable.
Which one fits depends on who answers the booking. A café that checks requests each morning can collect them itself; a restaurant with OpenTable managing its floor probably wants the second path so the booking lands where staff already look. The feature list does not say what the OpenTable connection consists of — a link, a widget or an embedded flow — so confirm it before you design the reservation page around it. Likewise, the theme supplies the on-site form element, but where submissions are stored and delivered is a documentation question, not a feature-list one.
A dedicated Restaurant page in the admin
Alongside the theme options, the vendor lists a Restaurant page in the admin panel. Paired with the menu post type and the reservation form, that points to one settings area for the food-business specifics, kept out of the header, footer and typography controls.
That separation pays off at handover: a manager changing the booking message opens the restaurant settings instead of learning a page builder, and the layouts stay untouched. The vendor does not enumerate the controls on that page, so treat its exact contents as something to inspect in a demo install. Site-wide decisions such as typography, header behaviour and global colour live in Mikado Options.
WPBakery and Revolution Slider ship inside the theme
Pages are composed in WPBakery Page Builder, which the vendor describes as included, alongside the included Revolution Slider. Both are wrapped into the theme, so their updates arrive with theme releases: version 2.1 (12 May 2026) updated WPBakery to 8.7.2 and Revolution Slider to 6.7.54, together with Mikado Core 1.6 and Mikado Restaurant 1.1.
That arrangement suits a site without a developer maintaining plugin subscriptions. It is less tidy if you already license WPBakery yourself, since you end up with two copies. The practical check is which plugin versions sit inside the theme folder, because bundled plugins do not update independently.
Compatibility attributes observed in the marketplace listing on 4 November 2026 name WooCommerce 10.x.x and 9.x.x, WPBakery Page Builder and WPML, with the software version field listing WordPress 7.0.x, 6.9.x, 6.8.x, 6.7.x, 6.6.x and 6.5.x as discrete entries. Those are vendor declarations attached to the product, not a record of anyone running Piquant on a current install. The same release notes mention improved PHP 8.3 compatibility and an updated Google Map API handling — maintenance signals rather than guarantees.
Two planning constraints: social feeds and demo photography
Version 2.1 removed the Mikado Instagram Feed and Mikado Twitter Feed plugins, citing API changes at both services, and dropped the twitter-connect script behind the Twitter Slider shortcode. Older feature lists still advertise Twitter and Instagram social widgets, so if social posts belong in your design, budget for a third-party feed plugin rather than assuming the theme supplies one.
The second constraint is imagery. The vendor states plainly that demo images are presentational only and cannot be used on your site without buying a licence from a stock library. For a food theme that is a real cost line, since the demo's appeal rests heavily on styled dish photography. The menu structure works regardless: entries accept your own images, and text-only lists remain available.
Questions & answers
Can I use the Piquant demo images on my live site?
No. The vendor states the demo images are presentational only and are not licensed for your site unless you buy them from a stock image library. Plan dish and interior photography as a separate budget item.
Does Piquant still include Instagram and Twitter feed widgets?
The version 2.1 changelog removed the Mikado Instagram Feed and Mikado Twitter Feed plugins because of API changes, and removed the Twitter Slider's connecting script, even though older feature lists still mention them. Use a third-party feed plugin if the site needs social posts.
Does Piquant handle reservations itself?
The vendor lists two options: a Restaurant Reservation Form shortcode for collecting requests on your site, and an OpenTable integration for venues already using OpenTable. How far the OpenTable connection goes is not described, so confirm it before building the reservation page.
Do I need a separate WPBakery licence?
The vendor describes WPBakery Page Builder and Revolution Slider as included with the theme, and the changelog shows both updated within theme releases. If you already hold your own WPBakery licence, you may end up maintaining two copies.
