How to Set Up Posting Templates in Acenda
Posting templates are the essential "plumbing" that connects your Acenda catalog data to various marketplaces. They allow you to create product listings that strictly adhere to specific marketplace requirements and attributes.
📺 Video Tutorial
Prefer to learn by watching? View our step-by-step video walkthrough on setting up templates here:
Watch: Setting Up Posting Templates (Vimeo)
Step 1: Access the Integration
Log into your Acenda Admin Tool.
Navigate to Integrations in the main menu.
Select the specific marketplace integration you wish to configure (e.g., Target+, Walmart, etc.).
Click the Edit button for that integration.
Step 2: Prerequisite (Recommended)
Before creating a category-specific template, we highly recommend setting up your Commonality template.
💡 Why? This establishes default field mappings that can be instantly applied to all future category-specific templates, saving you from mapping the same fields repeatedly.
If you haven't done this yet, please review our guide on Setting up Commonality for Channel Posting Templates.
If your Commonality template is already configured, proceed to Step 3.
Step 3: Create a New Posting Template
Click the Posting Templates tab within the integration.
Locate the Create New Template section.
Select the relevant category from the dropdown menu and click Create.
Find your new category template (usually at the top of the list) and click Edit.
🛑 Can't find your category?
If the category you need isn't in the dropdown, you may need to open a ticket with the marketplace to request approval for that category. Refer to our guide on Requesting New Category Approvals.
Step 4: Apply Commonality
Leverage the work you did in Step 2 to auto-fill the basics:
Scroll down to the footer menu of the template.
Locate the COMMONALITY tab.
Click the Uses (Count) button in the footer.
This will instantly map the default fields from your Commonality template to the applicable fields in this new category.
Step 5: Map Remaining Required Fields
After applying Commonality, you must map the remaining specific fields. These are easily identified as they will not have a blue COMMON badge next to them.
Tip: Click the Unmapped Req'd button in the footer menu to filter the view to required fields only.
For each field, select one of the following three mapping options:
Option | Description | Best Use Case |
1) String | A static value applied to all products in this template. | Constant values (e.g., setting "Adult" for an Age Group field). |
2) Property | Direct mapping to an existing Acenda field. | When product data matches the marketplace field exactly (e.g., Brand, Title). |
3) Twig | A formula used for dynamic content generation. | Logic, conditional formatting, or unit conversions. |
⚠️ Crucial Note: Unit Conversions
Many marketplaces (such as Target+ or Walmart US) strictly require Imperial values (e.g., pounds, inches).
If your Acenda Product Catalog data is stored in Metric (e.g., kilograms, centimeters), you must use a Twig formula to convert the data within the template.
Do not map the property directly, or you will send incorrect data (e.g., sending "5 kg" as "5 lbs").
Example Twig Conversion (Kilograms to Pounds):
If the marketplace requires lbs but your weight is in kg, use this Twig formula:
{{ variant.weight * 2.20462 }}
Handling Multi-Value Fields
Some attributes allow for multiple values (indicated by a "Max" value greater than 1).
Check the Box: You must check the Delimited box to enable multiple values.
The Separator: We strongly recommend using a pipe delimiter (|) to separate your values. Do not use a comma, as commas often appear within the data itself (e.g., "Red, Blue").
Step 6: Save Your Work
Once you have mapped all necessary fields—ensuring all Required fields are satisfied—click the Save button to finalize your posting template.