Terms
Labels on the field reference
Each field on the custom fields page is described with these labels.
Field ID: The tag the website theme uses to read the field, written in B@SE (Maropost’s template language). For example, [@misc12@] is custom field misc12. In cPanel you find the field by its name, not this tag.
Type: The kind of value the field holds, as set up on the custom field in cPanel. The types in use are:
- Boolean: a yes/no flag. cPanel shows it as a true/false control, but the theme receives it as
yorn. Set it with the control in cPanel. The theme reads three Boolean fields: misc12 (Direct Ship Only), misc25 (Special Order Only) and misc26 (Discontinued Run Out). - Short Text and Text: free text. Most custom fields are one of these, including the list fields. Maropost accepts any text, so the field type doesn’t stop a value in the wrong format. The format each field needs is on Product field formats.
- Integer: a whole number, such as misc14 (Estimated Lead Time, in days).
- Decimal Number: a number with decimals.
Section: The tab of the cPanel product editor where the field sits, such as Description, Images or Stock Control. It isn’t where the field shows on the website. For that, see Which fields work where.
Description: The help text saved on the custom field in cPanel. Some of it is out of date. Where it disagrees with Product field formats, follow the workflow page.
Used on Webstore: Whether the website theme reads the field. That covers showing it on the product page, product cards or cart, and using it to decide something, such as the availability label.
Used in Docs: Whether the field appears in Maropost documents, such as emails and printed documents.
Used in Config: Whether the field is used outside the website and documents, for example by product imports and exports.
Product terms
Custom field (misc field): One of Maropost’s numbered extra product fields (misc1, misc2 and so on). Altapac’s theme gives about 20 of them a specific job. See Product field formats.
Standard field: A product field Maropost has built in, such as Subtitle, Short Description or Date of arrival. The theme gives some of them a job you wouldn’t expect. See standard fields.
Website Design Template: The product field that picks the product page layout. Blank gives the standard product page. bikeRacks gives the bike-rack page. The value must match exactly, including capitals. See Set up a bike-rack product.
Item specific: A name and value pair on a product, such as Bikes Carried = 2 Bikes. The standard product page lists every item specific as a row in Specifications. The bike-rack page looks for 15 exact names to build its tiles and chips, and puts any other name in an “Other” group. The store caps each value at 150 characters.
On promotion (inpromo): Maropost’s state for a product whose promotion is running. Some things show only in this state, such as the promo image in misc11. While a promotion runs, the site uses the promotion price, not the customer group prices. See Run a promotion.
Price on request: A product whose price for the shopper is $0. The site shows “Contact us for price” and an enquiry button instead of a price. See Price on request and trade customers.
Trade customer: A customer in one of the “… - DT” trade tiers (customer groups 8 to 13). F&F - DT (group 7) and Wholesale (group 2) are not trade groups. Trade customers see ex-GST prices and no sale badges. See Price on request and trade customers.
Cross-sell: A product relationship set on the product in cPanel. On bike racks, cross-sells become the Add-ons section. On the standard product page they show in a “You May Also Like” row.
Not live yet: On altapac.com today, bike racks also repeat their cross-sells in a “You May Also Like” row further down the page. Dropping that duplicate row arrives with the next theme release (AUD-21).
Parent and child products: A product sold in options (sizes, colours, fitments) is a parent with a child product for each option.
Content type: The kind of content page in cPanel, such as Services, Promotions or Brand. Each has a code, and the theme finds some pages by that code, so the code must match exactly. Products are linked to vehicles by assigning them to parts-finder content pages. See Maintain the parts finder.