Table Of Contents

Contemporary design, The Palisades by AdVision is one of the most 'modern' themes available for the SEO Shop/Lightpeed eCom platform and it is a fully responsive, for smaller mobile devices and expands to the full width of any desktop monitor.

 'Bigger is Better' as The Palisades features significantly larger product images, beautiful roll over effects that incentivize your visitors interaction.

Features

All views Autocomplete search with product thumbnails

All views Sticky header

All views Mega Menu

All views Add to Cart animation

All views Live chat

All views Page loader with animation

Homepage Video section

Homepage Top Banner 'Down Arrow' functionality

Homepage Social media feeds

Homepage Masonry styled social media feeds

Homepage Newsletter signup popup on landing page

Homepage/ Grid Product hover /quick view function

Grid/Category View mode switch

If you require any other ‘online’ customization services or hosting, outside of your SEOshop

E-commerce web store theme, please don’t hesitate to contact the AdVision eCommerce Developement Team.

AdVision eCommerce - Suite 1402 - Office 327, 347 Fifth Ave. New York NY 10016

Below you will find a list of options available in terms of the areas of the theme you have the capability to update per your preference.

Logo

1. Logo
   Upload your logo (in PNG image format) to be shown in the header of the theme. Recommended size 260 x 60 pixels.

2. Favicon
   Upload company favicon. The favicon is a small icon image shown at the top of the browser window/tab. See http://www.favicon.cc/ for more information on creating a favicon for your website |
   
   

Background

1. Background Color
   Select the color for the website’s global background setting, specifically the body area (below the header and above the footer).

2. Background Image
   If you’d like to show a background image, you upload that image here. It will show in the background of the body of the website (on top of the background color selected above). You can control the position and repeating of the background image using the following two settings…

3. Background Position
   If using a background image, use this setting to determine where the image show show in the background.

4. Background Repeat
   If using a background image, use this setting to determine if the image should repeat in the background (i.e. like a tile).

Header

1. Background Color
   Select the background color to be used for the header (shows behind the semi-tranluscent topbar background).
2. Topbar Background Color
   Select the background color be used for the top bar (show above the navigation bar, list promo element and small menu including Wishlist, Shopping Cart, Login, Create an Account and Language menu)
3. Topbar Text/Link Color
   Select the color you’d like text and links to be in the topbar element
4. Topbar Promo URL
   If you’d like to link the promo element somewhere, enter that URL here. If you don’t want it to link anywhere, you can simply enter #
5. Topbar Promo Label
   Enter the label you’d like to show in promo (defaults to “Free Shipping”)
6. Topbar Promo Description
   Enter the description you’d like to show in the promo (defualts to “On All Orders”)

Navigation

1. Background Color
   Select the background color you’d like to use for the main navigation element (contains search box, logo, social icons, my cart summary and main menu)
2. Text/Link Color
   Select the color for text and links within the navigation element (effects social icons, my cart summary; does not effect main menu links which are controlled separately)
3. Link Hover Color
   Same as above setting, but this color will be used when hovering over links within the navigation bar.
4. Menu Link Color
   Select the color to use for root links in the main menu (root links are those tabs displayed in the navigation bar)
5. Menu Link Color
   Select color to use for root links when hovered over with cursor
6. Menu Link Bg Hover Color
   Select background color for root links when hovered over with cursor
7. Menu/Search Suggestion - Dropdown Background Color
   When you hover over a root menu link that has a submenu to display (like “Products”), a dropdown will show. This setting allows you to control the background color of that dropdown element. This is also used for the background color of the search suggestion dropdown.
8. Menu/Search Suggestion - Dropdown Link Color
   Select the color of links show in dropdown menu (also affects links in search suggestion dropdown).
9. Menu/Search Suggestion - Dropdown Link Hover Color
   Like the setting above, select the color to show for said links when hovered over by the cursor
10. Menu/Search Suggestion - Dropdown Link Hover Background Color
    Like the setting above, select the background color to show for said links when hovered over by cursor.
11. Search Suggestion - Dropdown Border Color
    Used for the search suggestion dropdown, you can set the border color of the dropdown element.
12. Link 1
    The main menu in navigation will show Products (with dropdown listing categories) along with four optional links (that you set here), followed by a link to your SEOShop blog (if being used) and a link to your Brands page. With the following settings (Link 1-4) you can add up to 4 links to show between Products and Blog in the main menu.
    
    The format to be used for these settings is the following: Label=Link
    
    So for example, if I want this link to be to our about us page, I could enter About Us=/service/about/ This would then show “About Us” as a root link the main menu, and if the user clicked on it would send them to “/service/about/” on your SEOShop.
    
    You can also enter external/absolute links as well. For example, I could link to google using the following: Google=http://google.com This would show a root link “Google” and if clicked on would send the user to google.com.
    
    If you don’t want this link to show, simple empty this setting’s value (i.e. delete the text)
13. Link 2
    Like “Link 1” setting, but will show after Link 1 in the main menu. If you don’t want this link to show, simple empty this setting’s value (i.e. delete the text).
14. Link 3
    Like the link settings above, but will show after Link 2 in the main menu. If you don’t want this link to show, simple empty this setting’s value (i.e. delete the text).
15. Link 4
    Like the link settings above, but will show after Link 3 in the main menu. If you don’t want this link to show, simple empty this setting’s value (i.e. delete the text).
16. Dropdown Ad 1 Image
    When a user hovers over the “Products” root link in the main menu, a drop down will appear to show your catalog’s categories menu, best selling products and four image ads. Using the following “Dropdown Ad” settings, you can control those image ads.
    
    Select the image you’d like to load for Ad 1 (in JPG image format), recommended size 270 x 160 pixels.
17. Dropdown Ad 1 Link
    If you want Ad 1 to link somewhere, enter that link here. You can enter either a relative (/service/about/) or absolute (http://google.com) URL.
18. Dropdown Ad 2 Image
    Select the image you’d like to load for Ad 2 (in JPG image format), recommended size 270 x 160 pixels.
19. Dropdown Ad 2 Link
    If you want Ad 2 to link somewhere, enter that link here. You can enter either a relative (/service/about/) or absolute (http://google.com) URL.
20. Dropdown Ad 3 Image
    Select the image you’d like to load for Ad 3 (in JPG image format), recommended size 270 x 160 pixels.
21. Dropdown Ad 3 Link
    If you want Ad 3 to link somewhere, enter that link here. You can enter either a relative (/service/about/) or absolute (http://google.com) URL.
22. Dropdown Ad 4 Image
    Select the image you’d like to load for Ad 4 (in JPG image format), recommended size 270 x 160 pixels.
23. Dropdown Ad 4 Link
    If you want Ad 4 to link somewhere, enter that link here. You can enter either a relative (/service/about/) or absolute (http://google.com) URL.

Breadcrumb/Sidebar

1. Text Color
   Select the color to use for text/links in the breadcrumb navigation and sidebar menus
2. Background Color
   Select the background color to use for breadcrumb navigation and sidebar menus
3. Hightlight Colors
   Select the color to use for highlighting active links in the breadcrumb navigation and sidebar menus
   
   

Footer

1. Logo
   Upload image (in PNG image format) to use for the footer logo in the copyright bar of footer (lower left corner). Recommended size 220 x 30 pixels. Also recommended that the PNG you upload use a transparent background.
2. Background Color
   Set the background color of the footer element. Footer includes the newsletter, social icons and footer navigation menus.
3. Label Color
   Set the color to use for labels in the footer element. Labels include Customer Service, Products, My Account, Get in Touch and Sign Up For Our Newsletter
4. Text/Link Color
   Set the color to use for text and links in the footer element.
5. Livechat License No.
   If you’d like to use Livechat on your SEOShop website, sign up for an account at https://www.livechatinc.com/, then simply enter your License No. here.

Colors

1. Body Text Color
   Select color to use for standard text within body area (between header/footer)
2. Highlight Color
   Select a highlight color to be used on miscellaneous elements throughout the site to draw attention
3. Link Color
   Global link color setting. Select the color you’d like to use for links throughout the site (more specific link color settings will override this)
4. Link (Hover) Color
   Select the color to use when user hovers over link with cursor (more specific link hover color settings will override this)

Button

1. Button - Text Color
   Select the color to use for text in standard button
2. Button (Hover) - Text Color
   Select the color to use for text in standard button when user hovers over button with cursor
3. Button - Background Color
   Select the background color to use for standard buttons throughout the site
4. Button (Hover) - Background Color
   Select the background color to use for standard buttons when user hovers over button with cursor
5. Highlight Button - Text Color
   Select the color to use for text in highlight button
6. Highlight Button (Hover) - Text Color
   Select the color to use for text in highlight button when user hovers over button with cursor
7. Highlight Button - Background Color
   Select the background color to use for highlight buttons throughout the site
8. Highlight Button (Hover) - Background Color
   Select the background color to use for highlight buttons when user hovers over button with cursor
   
   

Typography

1. Headings (Google Web Fonts)
   Select the font you’d like to use for headings in the site (see https://www.google.com/fonts to preview font families)
2. Standard (Google Web Fonts)
   Select font you’d like to use for standard text throughout site.
3. Button (Google Web Fonts)
   Select font you’d like to use for buttons throughout site.

Contact Details

1. Name
   Company name for use in theme
2. Address
   Company address, used in “Visit us at” section, just above footer
3. Phone number
   Company phone number, used in “Reach us by phone” section, just above footer
4. Email
   Company email, used in “Email inquiries to” section, just above footer

Features

1. Reviews
   Turn on to show product reviews
2. Newsletter
   Show newsletter form in footer
3. Brands
   Show brands link in main menu
4. Tags homepage
   Show tags on homepage
5. Products in category
   Show amount of products in the category
6. Kiyoh
   Shop ID to activate widget
7. Feedback Company
   Widget ID to activate
8. Show stock level
   Activate to display stock levels on product page
9. Show fulltitle
   Displays full title of product
10. Show Product Ad
    Activate to use theme’s product ads feature (see Setting Up Product Ads below)
11. # of Thumbnails Per Row
    Set to show the number of thumbnails to show per row for product thumbnails grid view

Images

1. Product image fit
2. Category image fit
3. Brand image fit
4. Product Detail Image Width
   Width (in pixels) you'd like your product images to display on the product details page
5. Product Detail Image Height
   Height (in pixels) you'd like your product images to display on the product details page

Social Media

1. Facebook
   Add your Facebook URL to display the Facebook icon in the header/footer
2. Twitter
   Add your Twitter URL to display the Twitter icon in the header/footer
3. Google+
   Add your Google+ URL to display the Google+ icon in the header/footer
4. Pinterest
   Add your Pinterest URL to display the Pinterest icon in the header/footer
5. Youtube
   Add your YouTube URL to display the YouTube icon in the header/ footer
6. Tumblr
   Add your Tumblr URL to display the Tumblr icon in the header/footer
7. Instagram
   Add your Instagram URL to display the Instagram icon in the header/footer

Homepage - Header

Settings to control the main (top of page, above navigation bar) banner sliders on the homepage.

1. Slide (1,2,3) - Label
   Enter the label (first piece of text showing on top of slide) to show with slide (e.g. “GuitarCenter”)
2. Slide (1,2,3) - Description
   Enter description (shows just below label; e.g. “We make intelligent projects…”)
3. Slide (1,2,3) - Link
   If you’d like the slide to link somewhere, you can enter the relative or absolute URL here. Leave empty to not link anywhere.
4. Slide (1,2,3) - Image
   Upload the larger image (in JPG image format) to use for slide (size 1800 x 847 pixels). This larger image will be used in larger screen environments (768px and wider)
5. Slide (1,2,3) - Mobile Image
   Upload smaller image (in JPG image format) to use for slide (size 767 x 361 pixels). This smaller image will be used in smaller screen environments (767px or less, mobile).

Homepage - About Us

Control the about us section on homepage (displays just below navigation bar)

1. Title
   Enter text to show for title of about us section (e.g. “A Little About Us”)
2. Description
   Enter text to show below about us title (e.g. “Guitar Center is the world’s …”)
3. Link
   Enter link to send user to when they click on “Read More” link
   
   

Homepage - Grid

Conrol the grid of images shown below the “Our Latest Products” section on the homepage.

1. Space (1,2,3,4,5,6) - Image
   Upload image to use in the space of grid. Images sizes for spaces are as follows:
   1 - 945 x 496 pixels
   2 - 470 x 496
   3 - 463 x 496
   4 - 443 x 1004
   5 - 449 x 496
   6 - 449 x 496
2. Space (1,2,3,4,5,6) - Use Hover Image
   Activate if you’d like to show a hover image when user hovers over this space
3. Space (1,2,3,4,5,6) - Link
   If you’d like to link this space somewhere, enter the relative or absolute URL to send user to on click
   
   

Homepage - Lower Banner

Control lower banner slider on homepage, just below Homepage Grid.

1. Slide (1,2,3)
   Upload larger image (1800px wide) as banner for this slide. This version will be used for screens larger than or equal to 768px wide.
2. Slide (1,2,3) - Mobile
   Upload smaller image (767px wide) as banner for this slide. This version will be used for screens smaller than 768px wide.
3. Slide (1,2,3) - Link
   Enter URL to link user to when slide is clicked on. If you don’t want to link anywhere, just enter #. If this field is left empty, slide will not be shown

Homepage - Top Reviews

Control top reviews section of homepage

1. Video URL
   Enter the full embed URL for the video on youtube (e.g. https://www.youtube.com/embed/TTzdcOcpyuE)
2. Video Size
   Enter the width and height of your video (i.e. widthxheigh, no spaces; e.g. 400x350)
3. Title
   Enter text for title, first piece of text to show just below video
4. Subtitle 1
   Enter text for subtitle, shows just below title
5. Subtitle 2
   Enter text for second subtitle, shows just after first subtitle
6. Show Banner after Top Reviews
   Activate if you’d like to show a banner after the top reviews video section
7. Banner Image after Top Reviews
   If showing banner, upload the image (in JPG image format) you’d like to use here for larger screens (image size 1800px wide). This version will be used for screens larger than or equal to 768px wide
8. After Top Reviews Banner Mobile Image
   If showing banner, upload a smaller image (in JPG image format) you’d like to use here for mobile screens (image size 1800px wide). This version will be used for screens smaller than 768px wide

Homepage - Tags

Control settings for tags section on homepage

1. Background Color
   Select the background color for section
2. Label Color
   Select the color of the label “Tags” in section

Homepage - Social Plugins

Control the social plugins displayed at the bottom of homepage

1. Google Plus User ID
   Enter user ID for your google plus account to show recent activities. Leave empty if you don’t want to display this plugin
2. Facebook URL
   URL to your facebook page to load facebook plugin on homepage. Leave empty if you don’t want to display this plugin
3. Twitter Timeline URL
   Your twitter URL page for timeline plugin to be displayed on homepage. Leave empty if you don’t want to display this plugin.
4. Twitter Timeline Widget ID
   Widget ID from your twitter account's timeline widget, loads timeline on homepage social plugin section.
5. Twitter Username
   Username for your twitter account, loads with plugin on homepage. This displays at the bottom of the plugin
6. Blog Logo (Mini)
   Display at the bottom of blog plugin. Recommend PNG format with transparent background, size 120 x 30 pixels.

Setting Up Product Ads

On the product view page of your webstore, the Palisade theme allows you to show a product ad image (below main product image, to left of description). To use this feature, you’ll need to a) activate the setting “Show Product Page Ad” and b) setup and assign product ad tags using the below instructions.

To use this product page ad feature, you need to setup product page ad tags. Each tag you setup is a separate ad which includes the image filename and link to send the user to if they click on said ad.

To create a new product page ad, start by uploading the image file for the ad by going to SEOShop admin>>Tools>>Files. Click Upload Files and select the image you want to use for the ad. It needs to be a valid web image format (PNG, JPG or GIF), recommended size for image is 370 x 370 pixels. Once you’ve uploaded the file, click on the URL text in that new files row and copy the URL value (CTL+C or mouse right-click>>copy).

Now that you’ve provided an image file for the ad and have the URL to that image file, the next step is to setup the tag for this product ad. In SEOShop admin, go to Products>>Tags, click Add a tag. For the tag to be used for the product page ad feature, the title of the tag needs to be formatted in exactly the following format: ProductAd:image_filename=link. So, for your new tag your title would start with “ProductAd:” followed by the URL of the image file you just uploaded (CTL+V or mouse right-click>>paste to paste the URL you previously copied). After filename, you need to type “=”, after which you can enter the relative or absolute URL you’d like the ad to link to.

For example, let’s say I want a product ad so I upload the image file and get the URL to another product on my site that I want it to link to, so I’m going to use the following...

Image filename = //static.webshopapp.com/shops/132178/files/062965058/product-ad.jpg

Link URL = /taylor-polytune-2-poly-chromatic-tuner.html

...with that information, my product tag’s title would be ProductAd://static.webshopapp.com/shops/132178/files/062965058/product-ad.jpg=taylor-polytune-2-poly-chromatic-tuner.html

Finally for your new product tag, set Visibility to Visible (so the tag will be available on the webstore), then click Save to create the new tag.

Now that you’ve setup a product ad tag, You can assign it to any product you want to use that particular ad. You can do this via SEOShop admin>>Catalog>>Products>>select Product>>Tags>>Apply the product ad tag you want to use. Only one product ad can be used per product, so if you assign multiple product ad tags to a product, the theme will only use the first one listed.

Note that these special product ad tags, if setup correctly as instructed above, will not display in the “Tags” listing of the product view page in your webstore (as they are not meant to be view by users).

Go to Top

Free Payment Gateway Providers

Certain providers like Authorize.net will charge monthly fees to sign-up for a Gateway service.  Other providers will include the gateway free of charge.

New Custom Payment Gateway Development

AdVision is able to integrate a custom payment gateway into your web store for an additional charge. The estimated timeline to build and test a new payment gateway is 4+ weeks due to the amount of testing and research that is typically required.

Here are the payment gateways we have built integrations for in eCom:

• Affirm
• AfterPay
• AlphaPay
• American Express China
• Authorize.net AIM
• Bambora
• Cayan
• CC Avenue
• Coin Payments
• Conekta
• Email Money Transfer
• Evo Snap
• First Atlantic
• First Data China
• Moneris
• Monetico
• PayDollar
• Pay Safe
• Plug n Pay
• Split It
• Touch Net
• Yed Pay
• Zip Pay

Our web stores can be fully customized to meet our client's design requirements and functionality via a selection of add-on / plugin modules, that enhance the sites owner's access to self administer other content pages over and above the products within the point-of-sale.

AdVison Services : advision-ecommerce.com

PCI Compliant Hosting - Trustwave Certified PCI Compliant Hosting for Secure Online transactions

SSL Certificates - Installed to ensure HTTPS (secure) channel access to payment processor

Security Scanning - 24/7 scanning for hack attempts, malware with removal support

eCommerce Web Store Design & Development - Modern & Contemporary designs, that value adds to your viewers perception

Add-On Functionality - Module based add ons, allow for more interactive viewers experience and owners self-administrative control

Custom Programming - You think of it, or have seen it somewhere, we can likely build it

Search Engine Optimization - Assures your web store, website or blog have been optimized and registered with Google

Support - Big or small jobs, we offer eCommerce platform support

Contact : 866 865 8783 or info@advision-ecommerce.com for detail

Social Media: Facebook Twitter Google Plus 

In the static page form you will see an area for Title and Meta description. . 

Title : It will be the name of the static page

Meta Description:  Its an area where you place some part of the text of the static page which has most important information as that will show on the online searches.

You can also add images or video to the text while also manage the formatting of the content on the custom pages using text editor features or SOURCE MODE via HTML of the page.

What is an "update cycle"?

Themes in eCom can be automatically updated by the theme's developer.  Developer's often release updates to themes to fix bugs, improve security or add on functionality.  If you edit your theme in eCom, it makes a copy of theme code in your site so you can customize it as you want, but this means any future updates for the theme will not be automatically applied (because you now have a custom theme).  You or the theme developer may be able to apply future updates manually, but this depends on the theme developer providing the necessary details for each update, and may require additional costs (for the manual work required to implement the updates).

What if I edit the theme and want to go back to into the update cycle?

It's possible, but it would require uninstalling your customized theme and reinstalling the standard theme from the marketplace, meaning you lose any customization work that had been done to the theme and you'd have to reapply any theme setting adjustments.

Can a theme be modified without editing it?

 Some changes can be implemented via custom javascript applied to your eCom account to modify the look of your site.  While the theme code won't be modified, with javascript, it is possible to modify the display of your site without editing the theme.  Using this method, the code of your site can be modified AFTER the page has loaded. This means your theme code is loading as intended, but is being modified on-the-fly by the javascript code.  This allows modifying the display of your website without editing the theme, however this method does have a couple down sides.  First, there can be a slight delay after page load before the javascript takes effect (though in most cases, this is negligible), and secondly, this method of development can take longer than directly editing the theme, meaning it can be a little more expensive in initial development costs, but it will allow you to keep your theme in it's update cycle.

1- Build Product Catalog in Lightspeed

2 - Understand Product Image Sizing

1- 'Building the Product Catalog' - Lightspeed Retail or eCom Support will be the best resource to help you through the Product Catalog creation and editing process within Lightspeed.

Having said that, we do have some advice for you as you build the Product Catalog. Make sure to consider the importance of 'meaningful descriptions' of at least 2 or 3 sentences, on each and every product.

The following article outlines the SEO advantage you will give your web store if you build out the product descriptions as outlined.

Article - How to Write Product Descriptions That Sell

Product Descriptions - The import tool for Lightspeed eCom is customer facing and has the fields for both short and long description. 

--

2- Sizing Images Correctly - AdVision is here to help and guide you on this process of sizing image, and we have the following suggestions from an eCom Development perspective for you.

Image Sizing - What you need to know.

When it comes to image sizing there is only one way to do it correctly and too many ways to get this wrong. We know that poorly sized or inconsistent image formatting will have a significant impact on the users experience (UX).

The following short movies will give you a basic understanding on the process of Image Sizing.

Movie - How to size Images & Why Sizing is so important

* If you have 100s or 1000's you need sized initially, you can ask us to size them for you. Just let me know how many and we can review and estimate that option for you. However, ultimately it is important you learn the process.

AdVision's - Recommended Sizing Guideline

During our meeting, we can decide on a format for your product images - Square, Horizontal or Vertical and you can then size as we recommend and upload the images into your Product Catalog.

Just do a few first and share back your results so we can confirm you are on track.

Here are the sizes we recommend....

Square - 1200 x 1200 | Horizontal - 1000 x 800 | Vertical - 800 x 1000 or for thin products such as bottles - 600 x 1000 |

* Sizes shown in pixels based @ 72 or 96 DPI, RGB - JPEG or PNG files continuous tone images, which a standard photograph. You should only use the GIF file format for halftone images, which are sold colors such as logos or artwork.

Formatting : You can choose more then one format for eg a category Bicycles may show better Horizontally vs Bike Accessories showing better as Square. If you do have different formats per categories, then ALL images in a given category should be the same format.

By sizing and formatting images correctly, this allows us to present to the visitor the experience of the images doubling in size as they browse page to page, example 300 x 300 Category Page, 600 x 600 Product Page, 1200 x 1200 Zoom.

We do not recommend having a 'hodge-podge' of sizes and formats loaded into your product catalog.

Summary : So PNG or JPEGS are ideal for your Product Catalog image you upload into Lightspeed, as outlined above and presently the only formats you can upload into Lightspeed.

But you will also be showing the visitor 'supporting images' as usually seen on the homepage, top of category pages, along side of the product images.

For those images, we have another file format we want you to save as. We recommended WebP image file format that is clearer, sharper and less file sizes then the product images (loads quicker).

• JPEG or PNG for Lightspeed Product Catalog Images

• WebP for all other 'Supporting Images'

--

How to Hold the Visitor's Attention, the secret is 'Consistency of Presentation'

AdVision's understands the influences of visual and functional elements within our eCommerce Web Stores, on Human browsing behavior.

Our Development Team, know that the Number 1 # Rule that will help extend the time someone browses on your Web Store is 'Consistency of Presentation'. This means that every page design and their elements, always should load the same size, place and shape as previous pages, with a degree of predictability and a comfortable flow for the 'eye', without having multiple elements competing and on a page for attention.

The Halo Effect of Perception, is a subconscious process your visitor experiences and transpires in under 120,000th of a second, each and every time they navigates through an eCommerce Web Store.

Example : Do I stay or do I go - am I interested or not - am I going to see, next, what I expect to see ? - are the primary questions, that are generally subconsciously assessed, prior to each 'click'.

To that point, Human Behavioral Science have determined that if the Web Store depicts 'Consistency of Presentation' - well balanced - that it will generally provide a positive feedback to the Visitor, each and every click.

During this process the Visitor essentially scores their browsing and is looking for a predictable Navigation in which they are experiencing an understandable design layout & easy to comprehend functionality.

This then categorizes within the Visitor - A Value Added Perception - of your company, that then establishes 'Trust'.

1. If you have not done so already, download the attached zip file to the computer that you want to install the extension on.
2. Extract the contents of the zip file to a location of your choice where it won't be moved or deleted.
3. Open a new Chrome browser window and navigate to the extensions page by typing chrome://extensions in the address bar and pressing the Enter key or by clicking on the three dots in the top right hand corner of the browser, selecting "More tools", and then Extensions.
4. Once the extensions page has loaded you will need to turn on "Developer mode" by clicking the slider in the top right of the page
   
   
5. Once "Developer mode" has been enabled you can install the extension by clicking the "Load unpacked" button on the left side of the screen
   
   
6. Browse to the location where you extracted the zip file in step 2 and click on "Select Folder"
7. The extension should be installed and you should see the extension showing on the page
8. You should now be able to navigate to your Lightspeed Retail account in your browser to use the extension

Once installed and setup, our Data Bridge app will allow for the syncing of order and catalog info between your Lightspeed R-series account and one or more Lightspeed C-series websites.  The Data Bridge can:

1. Automatically import new products from Retail into eCom
2. Detect and sync certain product changes from Retail to eCom
3. Automatically import new eCom orders into Retail
4. Detect and sync certain order changes from eCom to Retail and from Retail to eCom
5. Combine quantity on hand of products from multiple Retail shops and report that combined total as the stock quantity available in your eCom website(s); you can turn on/off combined quantity on hand per each eCom website
6. Turn on/off price syncing from Retail to eCom per each eCom website (i.e. you can have one eCom site sync pricing changes from Retail while another eCom website uses pricing you manage autonomously in that eCom's admin interface)
7. Each site can use QOH from one specified R-series location or combined QOH from all locations
8. Send each site's orders to a specified R-series location

Important Considerations

Here we'll highlight what the Data Bridge currently does and does not sync between Retail and eCom.

R-series to C-series Product Syncing

If you want the app to manage an item, the product must be created in Retail only.  The Data Bridge pushes new product data in one direction only, from Retail to eCom.  See the product field map below for more information.

Product Custom Fields, Tags, and Vendors do not sync between Retail and eCom with the Data Bridge.  If using Retail's e-commerce module, web short/long descriptions are not currently supported in the Data Bridge.

C-series to R-series Order Syncing

If you want the app to manage an order, the order must be created in C-series only.  The Data Bridge pushes new orders in one direction only, from C-series to R-series.  A sale created in Retail outside the app will not be managed or linked to an order in eCom by the app.

Limited data changes are synced by the app between R-series and C-series.  See the Order section further down for more information.

Please note the following limitations:

1. Quotes made in Retail are not reflected in eCom (or vice-versa).
2. Tags created in Retail are not reflected in eCom.
3. Refunds and returns are processed within Retail and are not reflected in eCom.

Preventing Data Loss

The Data Bridge app is intended to sync data between R-series and C-series, it is not intended to store data.  While the app does store some data, it's only for internal app logic (i.e. determining if product info has changed since last sync).  This data is not available to "reload" into eCom or Retail.  You should follow the Lightspeed help documentation regarding data backup and preventing data loss: https://retail-support.lightspeedhq.com/hc/en-us/articles/360019200693

Preparing Existing Catalog Data

Matching Field Between eCom(s) and Retail Products

If we're dealing with existing catalog data in any of your eCom sites, we'll need a field value to match between the product in eCom and the product in Retail (Lightspeed doesn't provide a unique field, that we can use, to match the items between the two systems). The fields we can use to match products are Custom SKU, Manufacturer SKU, or UPC. Whichever field you choose, you'd need to make sure the field value in each eCom matches the field value in LSR (so the app knows which products match between the two systems).  AdVision can work with you to help identify the best field to use for your catalog.

Once the bridge has matched existing catalog data, a matching unique value won't be a concern for any future new items processed through the bridge as the bridge will create it's own unique ID for each item it exports from Retail and imports into your eCom sites, so this matching field using a unique value only matters for this initial setup, you won't have to worry about it for future items.

eCom Product Sets

Version 2 of the bridge does NOT use product sets in C-series (due to their limitations). Any matrices in R-series will be created as a product in C-series, and the matrix items will be created as variants within that product.  This is the same way Lightspeed's omnichannel handles matrices between the two systems.

Settings

API Connection Credentials

The API connections between the app and your R-series account and your C-series sites will be setup by AdVision when your app is setup.  If API credentials need to be changed in the future, please contact AdVision support.

Account Settings

1. Alert emails: Set the email addresses you'd like to be alerted if the app errors in syncing any information
2. Currency Code: identifies the currency used in your R-series account.
3. R-series Shipping Item ID: Since Retail doesn't offer a "shipping cost" field, when creating an eCom sale in Retail, eCom has to assign the shipping cost to product setup in Retail that represents the shipping cost.  This "shipping item" needs to be setup in your Retail catalog as a non-inventory item with a price of 0.  When the app creates the eCom order as a sale in Retail, it will assign the shipping cost from the eCom order to the price of this shipping item in Retail. 
4. R-series Payment Fee Item ID: If any payment options you offer in eCom incur a payment fee, we'll setup an item in your Retail catalog to represent that cost.
5. R-series Out of Balance Payment Type ID: sometimes R-series and C-series calculate slightly different totals (usually a penny high or low).  If you wish the app to automatically handle this scenario, we can setup a special "Out of Balance" payment type in R-series, and when this issue occurs, the app will create a payment using the out of balance type to in the amount needed to "balance" the sale.  This allows the sale to be completed and inventory deducted.
6. Push Orders When: This determines when the app will push new eCom orders into Retail.  You can choose to have new eCom orders created as a Sale within Retail when a) the order is first created in eCom or b) when the order is marked as paid in eCom
7. Disable cancel order on sale void: by default, if the R-series sale is voided, the app will cancel the related C-series order.

Default Site Settings

These are the default settings the app will use for each site in your account.

Inventory

1. Combined Quantity: If you'd like the app to combine the stock qty from all shops into a compiled total, check this box.  When checked, for each product into your Retail catalog, the app will combine the quantity on hand of that product for each shop in your Retail account and report that total as the product's stock quantity to eCom.
2. R-series Inventory Location ID: if not using combined quantity, you can specify which location sites should read QOH from.

Matching

If we're dealing with existing catalog data in any of your eCom sites...

1. Match items using R-series field: select field to match in R-series
2. Match items using C-series field: select field to match in C-series sites
3. Skip items without a match: if enabled, app will not sync items from R-series if it can't find a matching item in C-series

Syncing

Criteria for Targeting Products

If you'd like to limit when the app pulls new or updated product information from Retail to eCom, you can indicate a particular field in Retail that has to be set to a specific value in order for the product to be synced to eCom. 

1. R-series Sync Flag Field: Select the field you'd like to use to determine if a product should be synced from Retail to eCom
2. R-series Sync Flag Value: Indicate the value that should be set in the selected field to determine if a product should sync from Retail to eCom.

For example, if I'm creating new products and don't want them sent to eCom until I'm sure they're completely setup, I could select a field here (that I'm not using for something else), like "Custom SKU", and indicate a specific value, like "ready to sync", to tell the app not to sync any products (new or changed) unless I've set the Custom SKU field to "ready to sync".

1. Visibility on creation: Determine visibility in C-series when the app creates a new variant
2. R-series Root Category ID: If you want to limit which categories are used in bridge sites, you can set a root category.  This indicates to the bridge to only use categories within the specified root category.  E.g. if you have categories like:
   
   Root A
   - Sub AA
   - Sub AB
   
   Root B
   - Sub BA
   - Sub BB
   
   If you set your root category to "Root B", only categories "Sub BA" and "Sub BB" would be used by the bridge.  Any other categories would be ignored.
3. Require Mapped Category: if working with existing catalog data in C-series, to avoid creating duplicate categories, enable this setting to require each category first be "mapped" (linked from C-series to R-series).  You can map categories under each site in Sites>>select site>>Categories>>click on category to link it to a R-series category.

Pricing

1. Sync Pricing: If enabled, indicates you'd like any pricing changes from Retail to update eCom website.  This is the default setting, which can be customized per each eCom website, if you so choose.
2. Pricing is Tax Inclusive: If checked, indicates that the pricing is setup to be tax inclusive.  This is the default setting, which can be customized per each eCom website, if you so choose.
3. R-series Price Level: Indicates which "price level" from your Retail catalog should be used for the sale price for items in eCom.  Required if syncing pricing
4. R-series "Old Price" Level: Indicates which "price level" from your Retail catalog should be used for the MSRP/regular price for items in eCom. Leave empty if you don't want the app to sync old price.

Ordering

1. R-series Order Location ID: Set the location ID you'd like the app to send eCom orders
2. R-series Order Employee ID: When creating a sale in Retail, the app needs to assign the sale to an employee.  Set to the chosen employee's numeric, system ID from Retail.
3. R-series Order Register ID: When creating a sale in Retail, the app needs to assign the sale to a register.  Set to the chosen register's numeric, system ID from Retail.
4. Only sync orders after: if you have past orders in C-series, you can set this value to ensure those old orders aren't handled by the bridge.

Taxes

1. Tax Categories: In order to match eCom taxes to Retail taxes, the tax name in eCom needs to be mapped to the sales tax numeric, system ID in Retail.  To do this, provide the eCom tax name, an equal sign, then the Retail sales tax ID, like so:
   
   VAT=1 
   
   So in this example, "VAT" is the tax name in eCom and "1" is the sales tax ID in Retail.  If you need to support multiple taxes, simply separate each by a comma, like so:
   
   VAT=1,GST=3
   
   In this example, we have eCom's VAT tax set to sales tax 1 in Retail, and eCom's GST mapped to sales tax 3 in Retail.
2. Auto-generate Tax Categories: if you're using automatically calculated taxes in eCom, it's best to activate this setting, which will create a tax category in Retail for each tax rate needed from an eCom order.  E.g. if a particular item in eCom order is being charged 4% state tax and 3% county tax, the bridge will ensure there is a tax category in Retail for that total tax rate of 7%.
3. Default Tax Category ID: if auto generating tax categories "By individual rates", set the tax category to create tax classes in.
4. Payment Methods: In order to match eCom payment methods to Retail payment options, the eCom payment method name needs to be mapped to the payment option's numeric, system ID in Retail.  To do this, provide the eCom payment method name, an equal sign, then the Retail payment option ID, like so:
   
   invoice=10
   
   So in this example, "invoice" is the payment method name in eCom and "10" is the payment option ID in Retail.  If you need to support multiple payment options, simply separate each by a comma, like so:
   
   invoice=10,authorize.net=5
   
   In this example, we have eCom's invoice payment method set to payment option 10 in Retail, and eCom's authorize.net method mapped to payment option 5 in Retail.
5. Currency Code: set the base currency code te sites use

Sites

Each eCom site's settings will use the default settings (specified above) unless you select to customize a setting for a particular site.  In addition to managing settings, you can:

• activate/deactivate the site in the app
• Check Site for Updates: app will read current site data and compare to app data to ensure everything is up to date.
• Install/Uninstall
• View Events, Orders, Products, Variants and Categories

Events

View a recent history of any data sync events that the Data Bridge has attempted.  Both errors and successes are listed here.  For each sync record, you can click to view details.  Any errors will be listed in red.

If you set the "Alert Email" setting (outlined in the Settings section above), errors can also be emailed to you to alert you to the problems as they occur.

Account >> Sales

Manage any R-series sales created from C-series orders through the bridge.

Account >> Items

Manage any items synced from R-series.

Account >> Matrices

Manage any matrices synced from R-series.

Account >> Categories

Manage any categories synced from R-series.

Sites >> Orders

View and search the products that have synced through the app, and force a manual sync for a product if you'd like.  Each product

Sites >> Products

Manage products imported from C-series sites.

Syncing Catalog Data

The Data Bridge app checks for new or updated items in Retail every five minutes.  If it detects any items that have been created or changed, it will attempt to create or update those items in the bridge data.  Any relevant data changes detected within the app will then be dispatched to C-series sites.

Below is an outline of the basic relations between Retail and eCom fields.  Some fields only sync when first creating the product in eCom, while others will sync whenever changes are made to the field for existing products.  "When" column indicates if the field is used with new ("Creation") or existing ("Updates") products, or both.

Some important notes about how the app works with your catalog information:

Matrices and Attribute Sets

If you're using matrices in your catalog setup in Retail, the Data Bridge will use the matrices and matrix items to create appropriate products/variants in eCom.*  Specifically, the app will take the matrix details from Retail and create a product within eCom.  Any matrix items will then be created as variants within that eCom product.

Brands

The app will take the Manufacturer assigned to an item in Retail and look for that as a Brand within C-series.  For example, if you set Manufacturer = "Acme" in Retail, the app will look for Brand = "Acme" in eCom.  If not found, the app will create the new Brand in eCom. 

The Data Bridge app works off the numeric, system generated IDs for manufacturer/brand, so changing the manufacturer's name in Retail will not cause the brand's name to update in eCom.  So if you want to update a manufacturer/brand's name, you'd need to:

a) manually change the name in both Retail and eCom, or

b) create a new manufacturer in Retail with the new name you want to use, then assign that new manufacturer to the items you want updated - this will cause the app to see the new Manufacturer, create a new brand with that manufacturer's name in eCom, and update the items in eCom with that new brand.

Categories

For each site in your Bridge, you can determine how categories should be handled.  You can choose to have the app automatically create new categories in a site - using the same category structure as R-series, or you can choose to "Require Mapping", which means each category in R-series needs to be pre-mapped to a category in the site.  Mapping allows you to customize the category structure in each site as you'd like, then mapping the R-series categories to the custom category structure in the site, so the Bridge knows where each item should be assigned.

With Mapping

If you choose to require mapping for a site's categories, you'll want to create any needed categories in the site, then under Sites>>Categories in Bridge admin, for each site category, you need to select an R-series category it should map to.  Any items assigned to that R-series category will then map the site category when syncing from R-series to the site.

Without Mapping

The app will take the Category assigned to an item in Retail and look for that category (including it's parent category - if any) within each site.  For example, if you set the category in Retail to Hardware>>Tools>>Hammers, the app will look for those three categories (Hardware, Tools, and Hammers) in the site.  If any of those categories are not found, the app will create them within the site.

The Data Bridge app works off the numeric, system generated IDs for categories, so changing a category's name in Retail will not cause the category's name to change in the site.  So if you want to update a category's name, you'd need to:

a) manually change the name in both R-series and the site, or

b) create a new category in R-series with the new name you want to use, then assign that new category to the items you want updated - this will cause the app to see the new Category, create the new category in site, and update the items in site with that new category.

Syncing New Products from Retail to Site(s)

When the app detects new items in R-series, it will attempt to create those same items in your sites(s) using the fields listed above in the product field map.  If the new product is using a new matrix in R-series, the Data Bridge will create a matching product in site and then create the individual product variants from Retail as variants in the site product. 

If you have "Sync Pricing" turned off in the app settings, when the app is creating a new product, the pricing from R-series is used for the initial creation of the item, but future pricing changes for that item would not sync if "sync pricing" is turned off.

Syncing Product Changes

When syncing changes for an existing item (a product that already exists in the site), the app checks the following fields for changes, and if it detects any changes, attempts to update the appropriate fields in your site(s):

1. Stock Qty: If quantity on hand for item has changed, app will update site product/variants with new stock qty
2. Pricing: If set to sync pricing from Retail, and one or more of the assigned "price level" prices has changed, app will update site product/variants with new pricing
3. Brand: If Retail item's Manufacturer field changes, updates product's Brand in site
4. Custom SKU: Updates eCom variant's Article Code
5. UPC (or EAN) : Uses UPC if set, if not set uses EAN; updates eCom variant's EAN field
6. Manufacturer SKU: Updates eCom variant's SKU
7. Default Cost: Updates eCom variant's Cost
8. Description: Updates eCom product/variant's Title
9. Image: If you add or change the main image assigned to a item Retail, the related eCom variant image will be updated
10. Category: Updates eCom product's primary category assignment

If you want to perform a manual sync for an item, go to Account >> Items in app admin, select item, then click "Sync from Backoffice to Sites". This will pull latest data from R-series into the bridge, then any changes deteced will be dispatched to the C-series sites.

Orders

The Data Bridge uses eCom's webhooks which alert the app when events occur with your eCom orders.  The events the app currently listens for are order created, order updated, and order paid.

Syncing New Orders from eCom to Retail

New orders are only synced in one direction, from eCom to Retail.  When the app is alerted to a new order from eCom, it will attempt to take that order and create the necessary sale to represent it in Retail.  Several settings, covered in the settings section above, are used to accomplish the appropriate sale creation in Retail:

1. R-series Order Location ID: Determines which shop the app should create the sale in
2. R-series Order Employee ID: Which employee to use to create the sale
3. R-series Order Register ID: Which register to use to create the sale
4. Tax Categories: Translates tax categories used in eCom to the sale's taxes setup in Retail
5. Payment Methods: Translates the payment method used in eCom to the sale's payment option in Retail
6. Retail Shipping Item ID: If there is any shipping cost in the eCom order, this item will be added to the Retail sale the cost of shipping will be set as this item's price (i.e. this item represents the order's shipping cost)

Note: if you're using multiple eCom sites in your Data Bridge, each of these settings can be customized per each eCom (if so desired).

When creating a sale, the app does the following:

1. Attempts to match all the items in the eCom order to items in your Retail catalog.  To match products between eCom and Retail, the app keeps a database matching each eCom's product IDs to the matching item's Retail item ID.  This is why it is essential that any products in your eCom catalog be created in Retail and imported into eCom by the Data Bridge app, otherwise if an item is ordered in eCom and the app doesn't have a record of it, it will fail to fully build the sale in Retail.
2. Takes the eCom order's customer information and attempts to find a matching customer in your Retail account.  The app does this by attempting to match the email address.  If it finds any customers with a matching email address, it will then make sure that the customer found matches (case-insensitive) the eCom customer's First Name, Last Name, State, Country, Zipcode and Address (Line 1).  If all that information matches, the app will use the exisitng customer's record in Retail.  If the app fails to find an already existing customer in Retail, it will create a new customer record in Retail to use with the new sale
3. If the eCom order has payments, the app will include the payment info (payment methods and amounts) when creating the Retail sale, and attempt to set the sale to completed.  If the payments on the eCom order don't meet or exceed the order's total due, the sale will be created, but will fail to be marked as completed.
4. If the eCom order has no payment information, the app will set completed to false for the new Retail sale.

eCom Order Marked as Paid

If an eCom order is not marked as paid when it's created, but is marked as paid in eCom at a later date, the app will be alerted to this and attempt to add the necessary payment information to the Retail sale and mark it completed.

Syncing Order Changes from eCom to Retail* 

* only for orders imported from eCom through the Data Bridge app

eCom will alert the Data Bridge if an order is updated.  Currently the app will update a Retail sale:

1. If order payment status is newly set to paid, add payment details to Retail sale and mark as paid
2. If order status is completed, completed shipped or completed picked up, set Retail sale to completed
3. If order status is cancelled, set Retail sale to not completed

Currently no other data is synced on order updates from eCom.

Syncing Sale Changes from Retail to eCom*

* only for orders imported from eCom through the Data Bridge app

The Data Bridge checks for updates to Retail sales every five minutes.  If the app detects that an order has been updated, it will updated the related eCom order:

1. If sale is newly voided, set eCom order status to cancelled

Currently no other data is synced on order updates from Retail.

If you want to perform a manual sync for an order, either from eCom-to-Retail or Retail-to-eCom, go to Site >> Orders, select the order, then click TBD ("Sync from Retail to eCom" or "Sync from eCom to Retail") for the order you want to sync. This performs a manual sync when clicked, which means the app grabs the order's current data from the one system and attempts to determine if any changes have been made to the order that should be synced to the other system.

In the evolving world of eCommerce, Google Merchant Center remains one of the most effective tools for getting products in front of high-intent shoppers.

Whether you’re using Shopify, WooCommerce, Lightspeed, Ecwid, BigCommerce, or a custom-built platform, Google Merchant still delivers where it counts: visibility, performance, and growth.

Google isn’t just a search engine , it’s where buying journeys begin. When properly integrated, Google Merchant allows your products to appear in Google Shopping Ads, Free Listings, Search, and Performance Max campaigns. This exposure can drive highly qualified traffic without requiring large advertising budgets.

The key to success lies in how well your product feed is managed. Manually uploading product data is inefficient and error-prone.

Today’s best practices involve using automated feeds and middleware solutions to ensure accurate, real-time syncing of inventory, pricing, and product information. This not only keeps listings compliant with Google’s requirements but also maximizes their visibility and click-through potential.

No matter your platform, middleware can act as the smart layer between your store and Google Merchant, optimizing feed structure, automating updates, and reducing manual work. For many retailers, this is the difference between mediocre performance and measurable growth.

At AdVision, we specialize in custom Google Merchant solutions tailored to your platform, catalog size, and marketing goals. Whether you're launching your first feed or optimizing an existing one, our team helps ensure you're positioned for success across Google’s powerful ecosystem.

CatalogPilot™ – AdVision eCommerce Inc.

(Traducción oficial al español)

1. Propósito y Alcance

Este Anexo de Tratamiento de Datos (“DPA”) forma parte integrante de los Términos y Condiciones aplicables entre AdVision eCommerce Inc. (“Proveedor”) y el cliente (“Responsable del Tratamiento”) en relación con el uso de los servicios de CatalogPilot™.

Este DPA regula las condiciones bajo las cuales el Proveedor procesa datos personales en nombre del Responsable del Tratamiento, de conformidad con las leyes de protección de datos aplicables, incluido el Reglamento (UE) 2016/679 (“RGPD”).

2. Naturaleza y Finalidad del Tratamiento

El Proveedor procesa datos personales únicamente en la medida necesaria para la prestación de los servicios de CatalogPilot™, incluyendo:

• Ingesta y sincronización de datos de catálogos de productos
  
  
• Generación y enriquecimiento de metadatos
  
  
• Procesamiento de contenidos relacionados con accesibilidad, SEO y cumplimiento normativo
  
  
• Alojamiento, registro y supervisión del sistema
  
  
• Flujos de trabajo automatizados y asistidos por IA
  
  
• Soporte técnico y atención al cliente
  
  

El tratamiento se realiza exclusivamente conforme a las instrucciones documentadas del Responsable del Tratamiento.

3. Categorías de Datos Personales

Dependiendo de los datos proporcionados por el Responsable del Tratamiento, las categorías de datos personales pueden incluir, entre otras:

• Datos de contacto profesionales (por ejemplo, nombre, dirección de correo electrónico)
  
  
• Contenido de catálogos que pueda contener datos personales
  
  
• Datos técnicos de uso y registros del sistema
  
  
• Datos de soporte y comunicaciones
  
  

CatalogPilot™ no está diseñado para procesar categorías especiales de datos personales conforme al Artículo 9 del RGPD.

4. Funciones y Responsabilidades

El Responsable del Tratamiento conserva la plena responsabilidad sobre:

• La legalidad del tratamiento
  
  
• La exactitud y licitud de los datos proporcionados
  
  
• El cumplimiento de las obligaciones de información y consentimiento
  
  

El Proveedor actúa exclusivamente como Encargado del Tratamiento y no determina los fines ni los medios del tratamiento.

5. Obligaciones del Proveedor

El Proveedor se compromete a:

• Tratar los datos únicamente conforme a instrucciones documentadas
  
  
• Garantizar la confidencialidad de los datos
  
  
• Aplicar medidas técnicas y organizativas adecuadas
  
  
• Asegurar que el personal autorizado esté sujeto a obligaciones de confidencialidad
  
  

6. Subencargados del Tratamiento

El Responsable del Tratamiento autoriza al Proveedor a recurrir a subencargados del tratamiento, incluidos aquellos utilizados para:

• Infraestructura y alojamiento en la nube
  
  
• Servicios de inteligencia artificial
  
  
• Facturación y procesamiento de pagos
  
  
• Sistemas de comunicación y soporte
  
  

El Proveedor garantiza que todos los subencargados estén sujetos a obligaciones de protección de datos equivalentes a las de este DPA.

7. Transferencias Internacionales de Datos

Los datos personales pueden ser tratados o almacenados fuera del Espacio Económico Europeo.

En dichos casos, el Proveedor implementará las garantías adecuadas, incluidas las Cláusulas Contractuales Tipo aprobadas por la Comisión Europea.

8. Seguridad del Tratamiento

El Proveedor aplica medidas de seguridad conforme al Artículo 32 del RGPD, incluyendo:

• Controles de acceso
  
  
• Cifrado cuando resulte apropiado
  
  
• Supervisión y registro de accesos
  
  
• Separación lógica de entornos
  
  

Los detalles adicionales se describen en la documentación de seguridad del Proveedor.

9. Notificación de Violaciones de Seguridad

En caso de una violación de la seguridad de los datos personales, el Proveedor notificará al Responsable del Tratamiento sin demora indebida y prestará asistencia para cumplir con las obligaciones legales de notificación.

10. Conservación y Eliminación de Datos

Tras la finalización de los servicios, el Proveedor eliminará o devolverá los datos personales, salvo que existan obligaciones legales de conservación.

11. Derechos de los Interesados

El Proveedor asistirá razonablemente al Responsable del Tratamiento en la atención de solicitudes de los interesados relacionadas con sus derechos (acceso, rectificación, supresión, limitación y portabilidad).

12. Asistencia en el Cumplimiento

El Proveedor prestará asistencia razonable para el cumplimiento del RGPD, incluidas las evaluaciones de impacto y las consultas previas, cuando sea aplicable.

13. Auditorías y Verificaciones

El Responsable del Tratamiento podrá realizar auditorías para verificar el cumplimiento, sujeto a:

• Notificación previa razonable
  
  
• Obligaciones de confidencialidad
  
  
• Alcance limitado a lo estrictamente necesario
  
  

Las auditorías presenciales solo se permitirán cuando la ley lo exija.

14. Confidencialidad

Las obligaciones de confidencialidad establecidas en este DPA continuarán vigentes tras la finalización de los servicios.

15. Responsabilidad

La responsabilidad del Proveedor en virtud de este DPA estará sujeta a las limitaciones de responsabilidad establecidas en los Términos y Condiciones.

16. Prelación de Documentos

En caso de conflicto entre este DPA y los Términos y Condiciones, este DPA prevalecerá en materia de protección de datos.

17. Modificaciones

Las modificaciones de este DPA serán notificadas al Responsable del Tratamiento y podrán aceptarse mediante el uso continuado de los servicios.

18. Legislación Aplicable

Este DPA se regirá por la legislación especificada en los Términos y Condiciones.

AdVision eCommerce Inc.

Vigente a partir del: 1 de enero de 2026

Esta Política de Privacidad describe cómo AdVision eCommerce Inc., una empresa constituida en el estado de Delaware, Estados Unidos (“AdVision”, “nosotros”, “nuestro”), recopila, utiliza, procesa, almacena, comparte y protege la información personal en relación con CatalogPilot y los servicios asociados (el “Servicio”).

Al acceder o utilizar el Servicio, usted acepta esta Política de Privacidad y cualquier documento incorporado por referencia.

Si no está de acuerdo, no debe utilizar el Servicio.

1. Alcance

Esta Política de Privacidad se aplica a:

• Comerciantes y usuarios autorizados
  
• Datos de comerciantes procesados mediante el Servicio
  
• Visitantes de nuestros sitios web
  
• Datos procesados con fines analíticos, de IA, soporte y administración
  

Esta Política no se aplica a:

• Sitios web de los comerciantes
  
• Sitios web de clientes finales de los comerciantes
  
• Plataformas de terceros integradas con el Servicio
  
• Contenido no controlado por AdVision
  

El tratamiento de datos por terceros se rige por sus propias políticas de privacidad.

2. Información que recopilamos

2.1 Información proporcionada por usted

• Información de cuenta (nombre, correo electrónico, empresa, teléfono)
  
• Identificadores de plataforma (claves API, tokens de acceso)
  
• Datos de catálogo y productos
  
• Imágenes de productos
  
• Comunicaciones de soporte
  
• Información de suscripción y facturación
  

No almacenamos datos de tarjetas de crédito.

Los pagos se procesan mediante proveedores externos (por ejemplo, Stripe).

2.2 Información recopilada automáticamente

• Dirección IP y ubicación aproximada
  
• Información del navegador y dispositivo
  
• Marcas de tiempo de acceso
  
• Registros de actividad de API y del sistema
  
• Registros de errores y rendimiento
  
• Eventos de seguridad y autenticación
  
• Datos de uso y telemetría
  

2.3 Datos de comerciantes

Los datos de comerciantes pueden incluir:

• Información de productos
  
• Títulos, descripciones, etiquetas y categorías
  
• Precios, variantes y metadatos
  
• Imágenes de productos
  
• Estructuras de catálogo
  

Estos datos pueden contener información personal si el comerciante la proporciona.

2.4 Datos de plataformas de terceros

Al conectar una tienda, podemos recibir:

• Datos del catálogo de productos
  
• Metadatos de inventario o logística (si están disponibles)
  
• Categorías, etiquetas y atributos
  
• Imágenes y contenido estructurado
  
• Información de disponibilidad
  
• Configuraciones de la tienda
  

Accedemos únicamente a los datos necesarios para prestar el Servicio.

2.5 Cookies

Utilizamos cookies y tecnologías similares para:

• Autenticación
  
• Gestión de sesiones
  
• Análisis
  
• Rendimiento
  
• Seguridad
  

Consulte nuestra Política de Cookies para más detalles.

3. Uso de la información

3.1 Prestación del Servicio

Utilizamos la información para:

• Importar y sincronizar catálogos
  
• Generar metadatos mediante IA
  
• Optimizar datos de productos
  
• Entregar contenido enriquecido
  
• Gestionar cuentas y facturación
  
• Proporcionar funciones de panel y administración
  

3.2 Mejora del Servicio

Utilizamos los datos para:

• Analizar uso y rendimiento
  
• Diagnosticar errores
  
• Mejorar modelos de IA
  
• Desarrollo de productos
  
• Garantizar estabilidad del sistema
  

Los datos agregados o anonimizados pueden utilizarse para análisis y aprendizaje automático.

3.3 Comunicaciones

Podemos comunicarnos con usted para:

• Onboarding
  
• Facturación
  
• Avisos del sistema
  
• Soporte al cliente
  
• Cambios en políticas o términos
  

3.4 Seguridad y cumplimiento

Procesamos datos para:

• Prevenir fraude y abuso
  
• Hacer cumplir los términos de uso
  
• Supervisión de seguridad
  
• Cumplimiento legal
  

4. Bases legales (UE / EEE / Reino Unido)

Tratamos los datos con base en:

• Ejecución de un contrato
  
• Interés legítimo (seguridad, mejora del producto)
  
• Consentimiento, cuando sea aplicable
  
• Obligaciones legales
  

5. Compartición de información

5.1 Proveedores de servicios

Podemos compartir datos con:

• Proveedores de hosting y nube
  
• Servicios de análisis y monitoreo
  
• Proveedores de IA
  
• Servicios de comunicación
  
• Procesadores de pago
  
• Herramientas de soporte
  

Todos están sujetos a obligaciones contractuales de confidencialidad.

Consulte nuestra DPA para más detalles.

5.2 Plataformas de terceros

Cuando se habilitan integraciones, los datos pueden compartirse con:

• Shopify
  
• Lightspeed
  
• WooCommerce
  
• BigCommerce
  
• Ecwid
  
• Google Merchant Center
  
• Otras plataformas compatibles
  

No somos responsables del tratamiento de datos por estas plataformas.

5.3 Requisitos legales

Podemos divulgar datos cuando lo exija la ley.

5.4 Transacciones corporativas

En caso de fusión, adquisición o reestructuración, los datos pueden transferirse.

6. Transferencias internacionales

Los datos pueden procesarse en Estados Unidos, Canadá, Europa u otros países, utilizando salvaguardas apropiadas como cláusulas contractuales estándar.

7. Retención de datos

Conservamos los datos:

• Mientras la cuenta esté activa
  
• Hasta 30 días tras la cancelación
  
• Más tiempo si lo exige la ley
  

Los datos anonimizados pueden conservarse indefinidamente.

8. Datos de clientes finales de los comerciantes

El comerciante es el responsable del tratamiento.

AdVision actúa como encargado del tratamiento.

9. Inteligencia artificial

CatalogPilot utiliza sistemas automatizados para enriquecer catálogos.

Todo contenido requiere aprobación explícita del comerciante antes de su publicación.

10. Seguridad de los datos

Aplicamos medidas técnicas y organizativas razonables, aunque no podemos garantizar seguridad absoluta.

11. Sus derechos

Según su jurisdicción, puede tener derecho a:

• Acceder
  
• Rectificar
  
• Eliminar
  
• Portabilidad de datos
  
• Oposición o limitación del tratamiento
  

Contacto: info@advision-ecommerce.com

12. California (CCPA)

No vendemos información personal.

13. Menores de edad

El Servicio no está destinado a menores de 18 años.

14. Violaciones de seguridad

Notificaremos incidentes conforme a la ley y a nuestra DPA.

15. Cookies

Consulte la Política de Cookies.

16. Documentos relacionados

• Términos y Condiciones
  
• Política de Uso Aceptable
  
• Política de Cookies
  
• DPA
  
• Prácticas de Seguridad
  

17. Cambios a esta política

Las actualizaciones entran en vigor al publicarse.

18. Contacto

AdVision eCommerce Inc.

Suite 1402 – 327, 347 Fifth Ave.

New York, NY 10016

📧 info@advision-ecommerce.com

Getting Started

1. How to Use This Manual

Core Navigation

2. Dashboard - Overview

3. Review Queue - Approval Workflow

Product Management

4. Products - List View

5. Products - Gallery View (A/B Comparison View)

6. Products - Detail View

7. Products - Images / ADA

8. Products - Variants

9. Products - SEO

10. Products - Attributes

11. Products - ESG

12. Products - Social

13. Products - Legal / PCI

14. Products - AI

15. Products - Activity & Errors

Categories Management

16. Categories - List View

17. Categories - Gallery View

18. Categories - Detail View

19. Categories - SEO

20. Categories - Social

21. Categories - ESG

22. Categories - AI

Connectivity

23. Connectivity - Incoming Catalog

24. Connectivity - Outgoing Delivery

Storefront Configuration

25. Storefront - Storefront Settings

26. Storefront - Schema & Brand Identity

27. Storefront - Users & Access Management

28. Storefront - Activity & Errors

29: Storefront - Language & Translation Controls

Billing & Payments

30. Billing - Overview

31. Billing - Usage

32. Billing - Invoices

33. Billing - Invoice Description

34. Billing - Payments

Reference

35. Glossary & Key Concepts 

36. The Invisible 80% How Modern Indexing Really Works

37. Why CatalogPilot Changes the Role of Your Catalog

38. How CatalogPilot Works (The Mental Model)

39. First-Time Workflow

40. Automatic vs Manual Processes

Each CatalogPilot invoice summarizes usage-based enrichment activity for a specific billing period. The description is designed to be readable at a glance, while still providing enough detail to trace every charge back to the system.

What the Description Represents

The invoice description follows this structure:

• Billing period
  
  The date range covered by the invoice (e.g., one week).
  
  
• Summary of enrichment activity
  
  A high-level count of what was processed during that period, such as:
  
  
• Fields enriched
  
• Images enriched and translated
  
• Products enriched and translated
  
• Variants enriched and translated
  
• Categories enriched
  

This is a summary, not a line-by-line ledger. CatalogPilot intentionally keeps invoices clean and readable rather than overwhelming merchants with raw logs.

Why It Appears as a Single Line Item

CatalogPilot bills enrichment usage as a single summarized line item per invoice period. This ensures:

• Clean, easy-to-understand invoices
  
• Totals that match exactly what was billed
  
• No confusion from dozens or hundreds of individual micro-charges
  

All detailed activity already lives inside the platform.

How to See the Full Breakdown

If you want to drill deeper into any number shown on an invoice:

1. Go to Billing → Usage
   This shows every enrichment action performed during the billing period.
   
   
2. Use filters and search
   Filter by date, subject (product, image, variant, category), or amount.
   
   
3. Click any activity entry
   You’ll see exactly:
   
   • What was enriched
     
   • When it occurred
     
   • Who initiated it
     
   • Whether it was assigned to an invoice
     
4. Cross-reference with Activity logs
   
   Activity logs elsewhere in CatalogPilot provide a complete timeline of approvals, edits, enrichments, and system actions.
   

Key Things to Know

• Invoice totals always reflect approved enrichment activity only
  
• Translations are billed separately (when applicable) and summarized in the description
  
• Subscription fees are not included in usage invoices and are billed separately
  
• A $0.00 balance simply means the invoice has already been paid or credited

The Category List View provides merchants with a structured, low-cognitive overview of all categories detected in their catalog and their relationship to enriched products. While categories are not enriched in isolation, they play a critical role in how product discovery, indexing, and navigation are structured across the storefront.

This view mirrors the Product List View in layout and behavior, with category-specific controls layered on top.

Purpose of the Category List View

The Category List View allows merchants to:

• See which categories are eligible for enrichment
  
• Control whether enriched category metadata is delivered to the storefront
  
• Navigate directly to related products within a category
  
• Review enrichment status without managing categories independently from products
  

Important: Categories exist to support and amplify product discovery. Only categories that contain products are eligible for enrichment.

Category Rows & Columns

Each row represents a single category and includes the following elements:

• Image
  
  Displays the category image when available.
  
  
• Enabled Toggle
  
  Controls whether enriched category metadata is actively delivered.
  
  
• Green: Enrichment delivery enabled.
  
• Orange: Enrichment delivery disabled (original storefront behavior only).
  
  
• Title
  
  The category name as defined by the platform.
  
  
• Language
  
  Indicates the language associated with the category record.
  
  
• Status
  
  
• Orange/Brown page icon: Category not yet enriched.
  
• Green checkmark: Category enriched and approved.
  
  
• Approved / Synced Date
  
  Shows when the category was last approved and delivered.
  
  
• Storefront Link Icon
  
  Opens the category directly on the live storefront.
  

Category → Product Relationship (Key Feature)

On the far right of each row is a purple eye icon with a number:

• The number indicates how many products belong to that category.
  
• Clicking the eye icon filters the Product List View to show only products within that category.
  
• Clicking the row itself opens the Category Gallery view.
  

This reinforces an important design principle:

Categories are not managed independently — they are always viewed in relation to their products.

Empty or Historical Categories

Some categories may appear with zero products. These are typically:

• Historical categories
  
• Legacy platform artifacts
  
• Empty organizational groupings
  

Categories with no products:

• Are displayed for visibility
  
• Are never enriched
  
• Do not affect billing or delivery
  

Delete Behavior

A red trash icon (left of the image column) allows merchants to delete a category record from CatalogPilot.

• Deleting a category removes it from CatalogPilot only.
  
• If the category still exists on the platform, it will be re-synced automatically and become eligible again in the future.
  

Header Controls & Filters

The Category List View includes the same global controls found in the Product List View:

• Not Yet Enriched (orange outline)
  
• View All Approved (green outline)
  
• Show All (neutral/gray outline)
  

Additional features include:

• Search field
  
• Filter drawer (status, inactive items)
  
• Column visibility selector
  
• Pagination controls at the bottom of the list
  

Review Awareness

If any products within categories are awaiting review:

• A blue badge appears in the header with the count.
  
• Clicking it redirects merchants to the Review Queue.
  

If no items are pending review:

• The badge turns green and displays zero.
  

Key Concept to Remember

Categories are structural amplifiers, not standalone entities.

They exist to:

• Support product discovery
  
• Improve crawler understanding of catalog hierarchy
  
• Extend enriched metadata across grouped products
  

Merchants are not expected to “manage” categories actively — the system handles this automatically based on product relationships.

The Product List View is the primary operational workspace for managing enriched products at scale. It is designed to be fast, low-cognitive, and safe — allowing merchants to control delivery without needing to inspect every underlying tag.

This view appears when selecting Products from the left navigation.

Purpose of the Product List View

The Product List View allows merchants to:

• See the current enrichment and delivery status of all products
  
• Enable or disable delivery per product
  
• Navigate quickly to detailed product records (Gallery View)
  
• Identify products awaiting review
  
• Control visibility without editing content
  
• Manage large catalogs efficiently
  

This view is not intended for deep editing. It is a control and navigation layer.

View Modes (Top Controls)

At the top of the list, merchants can switch between three modes:

• Not Yet Enriched (orange)
  Shows products that exist in the catalog but have not yet been enriched.
  
  
• View All Approved (green)
  Shows products that have been enriched and approved for delivery.
  
  
• Show All (neutral/gray)
  Shows all products regardless of enrichment state.
  
  

The selected mode highlights both the active button and the outline of the list, reinforcing context at a glance.

Review Indicator Badge

In the upper-right corner, a badge indicates whether products require review:

• Blue badge with a number (e.g. “6 Awaiting Review”)
  
  Clicking this sends the merchant directly to the Review page.
  
  
• Green badge showing zero
  
  Indicates no products require review.
  
  

This ensures merchants are always guided back to review before continuing.

Search, Filters, and Columns

Search

The search bar filters products by title in real time.

Filters

Filters allow merchants to:

• Filter by product status
  
• Hide inactive products
  
• Reset all filters easily
  

Columns

The Columns menu allows merchants to show or hide table columns, including:

• Image
  
• Enabled
  
• Title
  
• Language
  
• Status
  
• Approved date (replacing “Synced at”)
  

Column preferences affect display only and do not change product behavior.

Product Rows Explained

Each row represents a single product record.

Image

A thumbnail preview of the product image.

Enabled Toggle

Controls whether CatalogPilot delivers enriched content for that product.

• Green (On): Enriched content is delivered to the storefront.
  
• Orange (Off): Delivery is disabled; the storefront uses the platform’s original data.
  

This toggle allows merchants to disable delivery without deleting content.

Title

The product title for identification and navigation.

Clicking anywhere on the row opens the Product Gallery View (detailed record).

Language

Shows the language variant of the product record.

Status

A green checkmark indicates the product has been enriched and approved.

(Other states appear only before enrichment.)

Approved Date

Shows the most recent approval timestamp.

This replaces the earlier “Synced at” label and reflects merchant-approved state.

Sorting by this column surfaces recently approved products.

Storefront Link

A link icon on the far right opens the live product page on the merchant’s storefront.

Delete (Trash) Icon

A small trash icon appears to the left of each row.

• This removes the product from CatalogPilot’s active records.
  
• If the product remains active in the merchant’s platform, it will be re-imported and queued for enrichment again.
  
  

Deletion here does not remove the product from the storefront platform.

Pagination and List Size

At the bottom of the list:

• Merchants can choose how many products to display per page (e.g. 25, 50, 100).
  
• Pagination controls allow navigation across large result sets.
  

These controls affect display only and do not impact enrichment or delivery.

Design Philosophy

The Product List View is intentionally simple:

• No editing is required here
  
• No irreversible actions occur by default
  
• The focus is on status, control, and navigation
  

Deep inspection and editing happen in the Product Gallery View, which is covered in the next section.

The Storefront Settings section controls how approved CatalogPilot content is applied to your live storefront and how global delivery behavior is configured.

This page acts as the final control layer between enrichment and live delivery.

Site Identification

Site Name

Displays the name of the storefront connected to CatalogPilot. This is for reference only and does not affect delivery behavior.

Site URL

The live storefront URL where CatalogPilot delivers enriched content at render time.

This must match the storefront domain used by your platform.

Auto-Enrichment Controls (Support-Only)

Two advanced automation options appear here but are disabled by default:

• Auto-Enrich
  
• Auto-Approve Enriched
  

These features:

• Can only be enabled by CatalogPilot Support
  
• Require additional review and approval
  
• May require supplemental legal agreement
  

CatalogPilot defaults to manual approval to maintain enterprise-grade control and prevent unintended changes.

Enrich Variants (Global Variant Control)

Enrich Variants toggle controls whether variant-level enrichment is generated.

When enabled:

• Variants are treated as independent records
  
• Variant-specific schema and metadata are generated
  
• Variant images may be enriched
  
• Discoverability is amplified for each variant
  

When disabled:

• Variant pages inherit parent product content
  
• Variant pricing/SKU still come from the platform
  
• No variant-specific enrichment or estimates are created
  

This is the master override for all variant enrichment behavior.

Use Enriched Content on Site (Global Overrides)

This section lets merchants selectively disable delivery of enriched content for specific human-facing fields while keeping enrichment intact internally.

You may toggle delivery for:

• Title
  
• Alternate Title
  
• Short Description
  
• Long Description
  
• Meta Title
  
• H1 / H2 / H3
  
• Image Caption
  

When unchecked:

• CatalogPilot still enriches and stores content
  
• Original platform content is shown to visitors
  
• Structured metadata and machine-readable signals remain available unless disabled elsewhere
  

This allows merchants to:

• Preserve brand voice for human-visible copy
  
• Still benefit from structured data and indexing improvements
  

Language & Translation Settings (Reference)

A language selection area appears on this page listing supported languages.

Important notes:

• CatalogPilot does not create new languages
  
• Translations only apply to languages that already exist in your platform catalog
  
• Enabling a language assumes translated products already exist upstream
  
• Translation runs only after primary language enrichment is approved
  

Languages shown here act as opt-in delivery flags, not language creators.

Key Takeaway

Storefront Settings give merchants final authority over:

• What is delivered
  
• How it is delivered
  
• Whether variants are included
  
• Which enriched fields appear to humans
  

Enrichment can continue independently of delivery, ensuring safety, reversibility, and control.

Most merchants build their storefront for people.

Design, photography, layout, and descriptions are crafted for browsing. And that makes sense. Customers experience your store visually.

But search engines, compliance systems, accessibility crawlers, AI discovery engines, and marketplace indexers do not.

They interpret something else.

They do not evaluate “design.”

They do not measure “aesthetic quality.”

They do not reward visual polish.

They evaluate depth, hierarchy, relationships, and machine-readable clarity.

And in modern eCommerce, nearly 80% of discoverability happens within this invisible layer.

The Human View vs. The Machine View

To a shopper, a product page appears complete if it includes:

• A title
  
• A description
  
• Images
  
• Pricing
  
• Variants
  

To indexing systems, completeness is defined very differently.

Search and compliance systems evaluate:

• Heading hierarchy and semantic structure
  
• Canonical references
  
• Product-to-variant relationships
  
• Category reinforcement
  
• Accessibility attributes
  
• Structured product metadata
  
• Legal and compliance signals
  
• Data consistency across the entire catalog
  

Most of this exists behind the scenes.

When this foundation is incomplete, inconsistent, or shallow, search engines reduce confidence — even if the page appears fully developed to human visitors.

Depth Drives Discoverability

Modern indexing is no longer field-based. It is relationship-based.

Search engines and AI systems evaluate how:

• Products relate to categories
  
• Variants differentiate meaningfully
  
• Images reinforce accessibility compliance
  
• Metadata clarifies intent
  
• Structure remains consistent across the catalog
  

Without foundational depth:

• Smaller products become invisible
  
• Long-tail discoverability collapses
  
• Rich results diminish
  
• AI discovery engines misinterpret intent
  
• Compliance exposure increases
  

Catalog performance is not driven by design alone.

It is driven by systemic completeness.

The 80% You Don’t See

Native platforms provide surface-level product fields.

They were designed to:

• Display products
  
• Process transactions
  
• Manage inventory
  

They were not designed to build and maintain deep semantic architecture across every product, image, variant, and category.

Over time:

• Metadata drifts
  
• Accessibility attributes remain incomplete
  
• Variant clarity weakens
  
• Schema becomes outdated
  
• Compliance requirements evolve
  

This degradation is invisible to merchants — but measurable to indexing systems.

Equal Lift Across the Entire Catalog

CatalogPilot does not privilege high-volume products over smaller SKUs.

Every product receives the same depth of enrichment.

That means:

• Long-tail products gain visibility
  
• Lower-volume SKUs receive indexing clarity
  
• Variants become semantically distinguishable
  
• Categories reinforce intent
  
• Catalog-wide signals strengthen collectively
  

This is not selective optimization.

It is systemic elevation.

Dynamic, Not Static

Most storefronts operate statically.

Once created, structural data rarely evolves unless manually updated.

CatalogPilot operates dynamically.

As your catalog changes:

• Metadata is rebuilt
  
• Schema is refreshed
  
• Accessibility is reinforced
  
• Semantic signals are regenerated
  

This ensures:

• Indexing remains aligned with evolving standards
  
• Compliance does not decay
  
• Discoverability does not drift
  

Your catalog remains structurally current — not structurally stale.

Why This Matters Now

Modern search engines and AI systems evaluate far more than keywords.

They assess:

• Hierarchical clarity
  
• Semantic precision
  
• Accessibility readiness
  
• Compliance alignment
  
• Catalog-wide consistency
  

When foundational depth is weak, merchants often compensate by increasing paid traffic — driving up acquisition costs while underlying discoverability remains constrained.

Ignored products do not compete.

The invisible 80% determines whether your catalog is interpreted accurately — or filtered out.

The Systems That Actually Read Your Store

Modern storefronts are evaluated by dozens of indexing, compliance, and discovery systems. Below is a representative overview of how these systems interpret product data — and how CatalogPilot prepares your catalog to be understood correctly by them.

CatalogPilot does not control these systems. It prepares your catalog to be interpreted correctly by them.

This is the architectural layer most platforms never fully construct.

Where CatalogPilot Operates

CatalogPilot functions inside this invisible layer.

It:

• Reconstructs foundational depth
  
• Enhances machine-readable metadata
  
• Strengthens accessibility compliance
  
• Reinforces indexing clarity
  
• Operates non-destructively
  
• Delivers dynamically at render time
  

It does not change how your store looks.

It changes how it is understood.

Final Thought

If your storefront looks complete but underperforms, the issue may not be design.

It may be foundational.

And foundational depth is rarely visible — but it is always measured.

CatalogPilot was built specifically for that invisible 80%.

Table des matières

Fonctionnalités

Toutes les vues – Recherche avec complètement automatique et miniatures des produits

Toutes les vues – En-tête collant

Toutes les vues – Méga-menu

Toutes les vues – Animation d’ajout au panier

Toutes les vues – LiveChat

Toutes les vues – Chargeur de page avec animation

Page d’accueil – Section vidéo

Page d’accueil – Fonctionnalité « Flèche vers le bas » de la bannière supérieure

Page d’accueil – Fils de médias sociaux

Page d’accueil – Fils de médias sociaux style maçonnerie

Page d’accueil – Fenêtre pop-up d’abonnement à la newsletter sur la page de destination

Survol/Fonction d’affichage rapide des produits sur la page d’accueil/grille

Commutateur de mode d’affichage Grille/Catégorie

Si vous avez besoin de tout autre service de personnalisation « en ligne » ou d’hébergement en dehors du thème de votre site d’e-commerce en ligne SEOshop, n’hésitez pas à contacter l’équipe de développement d’AdVision eCommerce.

E-mail : info@advision-ecommerce.com

(Mailto:info@advision-ecommerce.com) Site web : advision-ecommerce.com (http://advision- ecommerce.com/)

Téléphone : +1 866 865 8783

AdVision eCommerce - Suite 1402 - Office 327, 347 Fifth Ave. New York NY 10016 - États-Unis

Vous trouverez ci-dessous une liste des options disponibles pour les éléments du thème que vous pouvez modifier selon vos préférences.

Logo

1. Logo
   Importez le logo (au format d’image PNG) à afficher dans l’en-tête du thème. La taille recommandée est de 260 x 60 pixels.

2. Favicon
   Importez la favicon de votre société. La favicon est une petite icône affichée en haut de la fenêtre/de l’onglet du navigateur. Pour en savoir plus sur comment créer une favicon pour votre site web, reportez-vous à http://www.favicon.cc/ (http://www.favicon.cc/)
   

Background (Arrière-plan)

1. Background Color (Couleur d’arrière-plan)
   Sélectionnez la couleur du paramètre d’arrière-plan général du site web, en particulier du corps de la page (sous l’en-tête et au-dessus du pied de page).

2. Background Image (Image d’arrière-plan)
   Si vous souhaitez afficher une image d’arrière-plan, c’est ici que vous l’importez. Elle s’affichera sur l’arrière-plan du corps de la page (au-dessus de la couleur d’arrière-plan sélectionnée plus haut). Vous pouvez contrôler la position et la répétition de l’image d’arrière-plan au moyen des deux paramètres suivants :

3. Background Position (Position de l’arrière-plan)
   Si vous insérez une image d’arrière-plan, utilisez ce paramètre pour indiquer à quel endroit de l’arrière-plan l’image s’affichera. 

4. Background Repeat (Répétition de l’arrière-plan)
   Si vous insérez une image d’arrière-plan, utilisez ce paramètre pour indiquer si l’image doit se répéter sur l’arrière-plan (comme une mosaïque).
   
   

Header (En-tête)

1. Background Color (Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser pour l’en-tête (affichée derrière l’arrière-plan semi-translucide de la barre supérieure).
2. Topbar Background Color (Couleur d’arrière-plan de la barre supérieure)
   Sélectionnez la couleur d’arrière-plan à utiliser pour la barre supérieure (affichée au-dessus de la barre de navigation, de l’élément en promo et du petit menu comprenant Wishlist (Liste d’envies), Shopping Cart (Panier), Login (Connexion), Create an Account (Créer un compte) et le menu Language (Langue).
3. Topbar Text/Link Color (Couleur du texte/des liens de la barre supérieure)
   Sélectionnez la couleur du texte et des liens affichés dans la barre supérieure.
4. Topbar Promo URL (URL promo de la barre supérieure)
   Si vous souhaitez créer un lien pour l’élément en promo, saisissez l’URL ici. Si vous ne souhaitez pas créer de lien, saisissez simplement #
5. Topbar Promo Label (Libellé promo de la barre supérieure)
   Saisissez le libellé que vous aimeriez afficher dans la promo (« Free Shipping » (Livraison gratuite) par défaut).
6. Topbar Promo Description (Description promo de la barre supérieure)
   Saisissez la description que vous aimeriez afficher dans la promo (« On All Orders » (Pour toutes les commandes) par défaut).
   
   

Navigation

1. Background Color (Couleur d’arrière-plan)
   Sélectionnez la couleur par défaut que vous aimeriez utiliser pour le principal élément de navigation (contient la zone de recherche, le logo, les icônes de médias sociaux, l’aperçu du panier et le menu principal).
2. Text/Link Color (Couleur du texte/des liens)
   Sélectionnez la couleur du texte et des liens du principal élément de navigation (affecte les icônes de médias sociaux et l’aperçu du panier ; n’affecte pas les liens du menu principal, qui sont contrôlés séparément).
3. Link Hover Color (Couleur de survol)
   Même chose que le paramètre précédent, mais cette couleur sera utilisée lors du survol des liens dans la barre de navigation.
4. Menu Link Color (Couleur des liens du menu)
   Sélectionnez la couleur à utiliser pour les liens racine dans le menu principal (les liens racine désignent les onglets affichés dans la barre de navigation).
5. Menu Link Color (Couleur des liens du menu)
   Sélectionnez la couleur des liens racine à utiliser lorsqu’on les survole avec le curseur.
6. Menu Link Color (Couleur des liens du menu)
   Sélectionnez la couleur des liens racine à utiliser lorsqu’on les survole avec le curseur.
7. Menu/Search Suggestion - Dropdown Background Color (Menu/Suggestion de recherche - Couleur d’arrière-plan du menu déroulant)
   Lorsque vous survolez un lien d’un menu racine avec un sous-menu à afficher (comme « Products » (Produits)), un menu déroulant s’affiche. Ce paramètre vous permet de contrôler la couleur d’arrière-plan de ce menu déroulant. Il sert également pour la couleur d’arrière-plan du menu déroulant dans les suggestions de recherche.
8. Menu/Search Suggestion - Dropdown Link Color (Menu/Suggestion de recherche - Couleur des liens du menu déroulant)
   Sélectionnez la couleur des liens affichés dans le menu déroulant (affecte également la couleur des liens dans le menu déroulant des suggestions de recherche).
9. Menu/Search Suggestion - Dropdown Link Hover Color (Menu/Suggestion de recherche - Couleur de survol des liens du menu déroulant)
   Comme pour le paramètre précédent, sélectionnez la couleur à afficher pour les liens des menus déroulants lorsqu’on les survole avec le curseur.
10. Menu/Search Suggestion - Dropdown Link Hover Background Color (Menu/Suggestion de recherche - Couleur d’arrière-plan de survol des liens du menu déroulant)
    Comme pour le paramètre précédent, sélectionnez la couleur d’arrière-plan à afficher pour les liens des menus déroulants lorsqu’on les survole avec le curseur.
11. Search Suggestion - Dropdown Border Color (Suggestion de recherche - Couleur du bord du menu déroulant)
    Sélectionnez la couleur du bord du menu déroulant des suggestions de recherche.
12. Link 1 (Lien 1)
    Le menu principal de la navigation indique Products (avec un menu déroulant des catégories) et quatre liens facultatifs (que vous définissez ici), suivis d’un lien vers votre blog SEOShop (si vous en utilisez un) et d’un lien vers la page de vos marques. Avec les paramètres suivants (Link 1-4), vous pouvez ajouter jusqu’à
    quatre liens à afficher entre Products et Blog dans le menu principal. 

13. Link 2 (Lien 2)
    Similaire au paramètre « Link 1 », mais il sera affiché après le premier lien dans le menu principal. Si vous ne souhaitez pas que ce lien soit affiché, ne saisissez aucune valeur pour ce paramètre (supprimez le texte).

14. Link 3 (Lien 3)
    Similaire aux paramètres du lien ci-dessus, mais il sera affiché après le deuxième lien dans le menu principal. Si vous ne souhaitez pas que ce lien soit affiché, ne saisissez aucune valeur pour ce paramètre (supprimez le texte).

15. Link 4 (Lien 4)
    Similaire aux paramètres du lien ci-dessus, mais il sera affiché après le troisième lien dans le menu principal. Si vous ne souhaitez pas que ce lien soit affiché, ne saisissez aucune valeur pour ce paramètre (supprimez le texte).

16. Dropdown Ad 1 Image (Image publicitaire 1 du menu déroulant)
    Lorsqu’un utilisateur survole le lien racine « Products » dans le menu principal, un menu déroulant apparaît pour afficher les catégories de votre catalogue, vos produits les plus vendus et quatre images publicitaires. En utilisant les paramètres « Dropdown Ad » ci-dessous, vous pouvez contrôler ces images publicitaires.

17. Dropdown Ad 1 Link (Lien publicitaire 1 du menu déroulant)
    Si vous souhaitez que la pub 1 renvoie quelque part, saisissez le lien de la destination ici. Vous pouvez saisir soit une URL relative
    (/Service/about/), soit une URL absolue (http://google.com (http://google.com)).

18. Dropdown Ad 2 Image (Image publicitaire 2 du menu déroulant)
    Sélectionnez l’image que vous aimeriez charger pour la pub 2 (au format JPG) ; la taille recommandée est de 270 x
    160 pixels.
19. Dropdown Ad 2 Link (Lien publicitaire 2 du menu déroulant)
    Si vous souhaitez que la pub 2 renvoie quelque part, saisissez le lien ici. Vous pouvez saisir soit une URL relative
    (/Service/about/), soit une URL absolue (http://google.com (http://google.com)).
20. Dropdown Ad 3 Image (Image publicitaire 3 du menu déroulant)
    Sélectionnez l’image que vous aimeriez charger pour la pub 3 (au format JPG) ; la taille recommandée est de 270 x
    160 pixels.
21. Dropdown Ad 3 Link (Lien publicitaire 3 du menu déroulant)
    Si vous souhaitez que la pub 3 renvoie quelque part, saisissez le lien ici. Vous pouvez saisir soit une URL relative
    (/Service/about/), soit une URL absolue (http://google.com (http://google.com)).

22. Dropdown Ad 4 Image (Image publicitaire 4 du menu déroulant)
    Sélectionnez l’image que vous aimeriez charger pour la pub 4 (au format JPG) ; la taille recommandée est de 270 x
    160 pixels.

23. Dropdown Ad 4 Link (Lien publicitaire 4 du menu déroulant)
    Si vous souhaitez que la pub 4 renvoie quelque part, saisissez le lien de la destination ici. Vous pouvez saisir soit une URL relative
    (/Service/about/), soit une URL absolue (http://google.com (http://google.com)).
    
    

Breadcrumb/Sidebar (Fil d’Ariane/Barre latérale)

1. Text Color (Couleur du texte)
   Sélectionnez la couleur à utiliser pour le texte/les liens dans le fil d’Ariane et les menus de la barre latérale.

2. Background Color (Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser pour le fil d’Ariane et les menus de la barre latérale.

3. Hightlight Colors (Couleurs de surlignage)
   Sélectionnez la couleur de surlignage à utiliser pour les liens actifs dans le fil d’Ariane et les menus de la barre latérale.

   
   

Footer

1. Logo
   Importez l’image (au format PNG) à utiliser pour le logo de la barre de copyright du pied de page (coin inférieur gauche). La taille recommandée est de 220 x 30 pixels. Nous recommandons également d’utiliser un arrière-plan transparent pour le fichier d’image PNG importé.

2. Background Color (Couleur d’arrière-plan)
   Définissez la couleur d’arrière-plan du pied de page. Le pied de page inclut la newsletter, les icônes de médias sociaux et des menus de navigation.

3. Label Color (Couleur du libellé)
   Définissez la couleur à utiliser pour les libellés dans le pied de page. Les libellés incluent Customer Service (Service client), Products (Produits), My Account (Mon compte), Get in Touch (Nous contacter) et Sign Up For Our Newsletter (S’inscrire à notre newsletter).

4. Text/Link Color (Couleur du texte/des liens)
   Définissez la couleur à utiliser pour le texte et les liens dans le pied de page.

5. Livechat License No. (N° de licence Livechat)
   Si vous souhaitez utiliser Livechat sur votre site web SEOShop, créez un compte à l’adresse https://www.livechatinc.com/ (https://www.livechatinc.com/), puis saisissez ici votre numéro de licence.
   
   

Couleurs

1. Body Text Color (Couleur du texte du corps)
   Sélectionnez la couleur à utiliser pour le texte standard dans le corps de la page (entre l’en-tête et le pied de page).

2. Hightlight Color (Couleur de surlignage)
   Sélectionnez la couleur à utiliser pour différents éléments du site afin d’attirer l’attention.

3. Link Color (Couleur des liens)
   Paramètre de couleur global des liens. Sélectionnez la couleur que vous souhaiteriez utiliser pour les liens à travers tout le site
   (les paramètres de couleur des liens plus spécifiques prévaudront).

4. Link (Hover) Color (Couleur (de survol) des liens)
   Sélectionnez la couleur à utiliser lorsqu’un utilisateur survole un lien avec son curseur (les paramètres de couleur de survol des liens plus spécifiques prévaudront).
   
   

Bouton

1. Button - Text Color (Bouton - Couleur du texte)
   Sélectionnez la couleur à utiliser pour le texte des boutons standard.

2. Button (Hover) - Text Color (Bouton (survol) - Couleur du texte)
   Sélectionnez la couleur à utiliser pour le texte des boutons standard lorsqu’un utilisateur survole un bouton avec le curseur.

3. Button - Background Color (Bouton - Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser avec les boutons standard à travers tout le site.

4. Button (Hover) - Background  Color (Bouton (survol) - Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser pour les boutons standard lorsqu’un utilisateur survole un bouton avec le curseur.

5. Highlight Button - Text Color (Bouton en surbrillance - Couleur du texte)
   Sélectionnez la couleur à utiliser pour le texte des boutons en surbrillance.

6. Highlight Button (Hover) - Text Color (Bouton en surbrillance (survol) - Couleur du texte)
   Sélectionnez la couleur à utiliser pour le texte des boutons en surbrillance lorsqu’un utilisateur survole un bouton avec le curseur.

7. Highlight Button - Background Color (Bouton en surbrillance - Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser avec les boutons en surbrillance à travers tout le site.

8. Highlight Button (Hover) - Background Color (Bouton en surbrillance (survol) - Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan à utiliser pour les boutons en surbrillance lorsqu’un utilisateur survole un bouton avec le curseur.
   
   
   

Typographie

1. Headings (Google Web Fonts) (Titres (Google Web Fonts))
   Sélectionnez la police que vous aimeriez utiliser pour les titres du site (reportez-vous à https://www.google.com/fonts
   (https://www.google.com/fonts) pour un aperçu des familles de polices).

2. Standard (Google Web Fonts)
   Sélectionnez la police que vous aimeriez utiliser pour le texte standard du site.

3. Button (Google Web Fonts) (Bouton (Google Web Fonts))
   Sélectionnez la police que vous aimeriez utiliser pour les boutons du site.
   

Coordonnées

1. Name (Nom)
   Nom de la société à utiliser dans le thème.

2. Address (Adresse)
   Adresse physique de la société, utilisée dans la section « Visit us at » (Rendez-nous visite au), juste au-dessus du pied de page.

3. Phone number (Numéro de téléphone)
   Numéro de téléphone de la société, utilisé dans la section « Reach us by phone » (Contactez-nous par téléphone), juste au-dessus du pied de page.

4. Email (E-mail)
   Adresse e-mail de la société, utilisée dans la section « Email inquiries to » (Posez vos questions par e-mail à l’adresse), juste au-dessus du pied de page.
   
   

Fonctionnalités

1. Reviews (Commentaires)
   Activez pour afficher les commentaires sur les produits.

2. Newsletter
   Affichez le formulaire de newsletter dans le pied de page.

3. Brands (Marques)
   Affichez le lien des marques dans le menu principal.

4. Tags homepage (Balises page d’accueil)
   Affichez les balises sur la page d’accueil.

5. Products in category (Produits dans la catégorie)
   Afficher la quantité de produits dans la catégorie

6. Kiyoh
   ID de boutique pour activer le widget

7. Feedback Company (Commentaire sur la société)
   ID de widget à activer

8. Show stock level (Afficher le niveau de stock)
   Activez pour afficher les niveaux de stock sur une page de produits.

9. Show fulltitle (Afficher le titre complet)
   Affiche le titre complet du produit.

10. Show Product Ad (Afficher la publicité produit)
    Activez pour utiliser la fonctionnalité de publicités produit du thème (voir Configurer des publicités produit ci-dessous).

11. # of Thumbnails Per Row (Nb de miniatures par ligne)
    Activez pour afficher le nombre de miniatures à afficher par ligne pour la vue de grille des miniatures de produits.
    
    

Images 

1. Product image fit (Ajuster l’image du produit)
2. Category image fit (Ajuster l’image de la catégorie)

3. Brand image fit (Ajuster l’image de la marque)
   Largeur (en pixels) que vous voulez donner à vos photos de produits sur la page de détails du produit

4. Product Detail Image Width (Largeur de l’image des détails du produit)
   Largeur (en pixels) à laquelle vous souhaitez afficher les images de vos produits sur la page des détails du produit.

5. Product Detail Image Height (Hauteur de l’image des détails du produit)
   Hauteur (en pixels) à laquelle vous souhaitez afficher les images de vos produits sur la page des détails du produit.
   
   

Médias sociaux

1. Facebook
   Ajoutez votre URL Facebook pour afficher l’icône de Facebook dans l’en-tête/le pied de page.
2. Twitter
   Ajoutez votre URL Twitter pour afficher l’icône de Twitter dans l’en-tête/le pied de page.
3. Google+
   Ajoutez votre URL Google+ pour afficher l’icône de Google+ dans l’en-tête/le pied de page.
4. Pinterest
   Ajoutez votre URL Pinterest pour afficher l’icône de Pinterest dans l’en-tête/le pied de page.
5. Youtube
   Ajoutez votre URL YouTube pour afficher l’icône de YouTube dans l’en-tête/le pied de page.
6. Tumblr
   Ajoutez votre URL Tumblr pour afficher l’icône de Tumblr dans l’en-tête/le pied de page.
7. Instagram
   Ajoutez votre URL Instagram pour afficher l’icône d’Instagram dans l’en-tête/le pied de page.
   
   

Page d’accueil - En-tête

Paramètres pour contrôler les diapos de la bannière principale (en haut de la page, au-dessus de la barre de navigation).

1. Slide (1,2,3) - Label (Diapo (1,2,3) - Libellé)
   Saisissez le libellé (la première partie du texte affiché en haut de la diapo) à afficher avec la diapo (p. ex., « GuitarCenter »).

2. Slide (1,2,3) - Description (Diapo (1,2,3) - Description)
   Saisissez une description (affichée juste en dessous du libellé, p. ex., « Nous créons des projets intelligents »).

3. Slide (1,2,3) - Link (Diapo (1,2,3) - Lien)
   Si vous souhaitez que la diapo renvoie quelque part, saisissez ici l’URL relative ou absolue de la destination. Si vous ne souhaitez pas que la diapo renvoie vers une destination, laissez vierge.

4. Slide (1,2,3) - Image (Diapo (1,2,3) - Image)
   Importez l’image la plus grande (au format JPG) à utiliser pour la diapo (1800 x 847 pixels). Cette image plus grande sera utilisée pour les écrans plus larges (768 pixels et plus).

5. Slide (1,2,3) - Mobile Image (Diapo (1,2,3) - Image mobile)
   Importez une image plus petite (au format JPG) à utiliser pour la diapo (767 x 361 pixels). Cette image plus petite sera utilisée pour les écrans plus petits (768 pixels ou moins, appareils mobiles).
   
   

Homepage - About Us (Page d’accueil - Nous connaître)

Contrôle la section « Nous connaître » de la page d’accueil (s’affiche juste en dessous de la barre de navigation). 

1. Titre
   Entrez le texte à afficher comme titre de la section à propos de nous (par exemple, «Un peu plus sur nous»)
2. La description
   Saisissez le texte à afficher sous le titre de la section « Nous connaître » (p. ex., « Guitar Center est un magasin de musique... »).
3. Link
   Saisissez l’URL de la destination vers laquelle renvoyer l’utilisateur lorsqu’il clique sur le lien « Read More » (Lire la suite).
   
   

Homepage - Grid (Page d’accueil - Grille)

Contrôle la grille d’images affichées sous la section « Our Latest Products » (Derniers produits) sur la page d’accueil.

1. Space (1,2,3,4,5,6) - Use Hover Image (Espace (1,2,3,4,5,6) - Utiliser image de survol)
   Activez cette option si vous souhaitez afficher une image en superposition lorsqu’un utilisateur survole cet espace.
   De 1 à 945 x 496 pixels
   2 - 470 x 496
   3 - 463 x 496
   4 - 443 x 1004
   5 - 449 x 496
   6 - 449 x 496
2. Space (1,2,3,4,5,6) - Link (Espace (1,2,3,4,5,6) - Lien)
   Si vous souhaitez que cet espace renvoie quelque part, saisissez l’URL relative ou absolue de la destination où renvoyer l’utilisateur lorsqu’il clique dessus.
   Homepage - Lower Banner (Page d’accueil - Bannière inférieure)
3. Space (1,2,3,4,5,6) - Link
   Si vous souhaitez lier cet espace quelque part, entrez l'URL relative ou absolue à laquelle envoyer l'utilisateur sur un clic.
   
   

Page d'accueil - Basse Bannière

Contrôle inférieur bannière curseur sur la page d'accueil, juste ci-dessous Home Grid

1. Slide (1,2,3)
   Téléchargez une image plus grande (1800px de large) en tant que bannière pour cette diapositive. Cette version sera utilisée pour les écrans supérieurs ou égaux à 768 pixels de large.
2. Slide (1,2,3) - Mobile
   Importez une image plus petite (767 pixels de large) en tant que bannière pour cette diapositive. Cette version sera utilisée pour les écrans plus petits que 768px large.
3. Slide (1,2,3) - Lien
   Entrez l'URL pour lier l'utilisateur à l'utilisateur lorsque vous cliquez sur la diapositive. Si vous ne souhaitez pas créer de lien, entrez simplement #. Si ce champ est laissé vide, la diapositive ne sera pas affichée
   
   

Homepage - Top Reviews (Page d’accueil - Meilleurs commentaires)

Contrôle la section « Top Reviews » (Meilleurs commentaires) de la page d’accueil.

1. Video URL (URL de la vidéo)
   Saisissez l’URL intégrée complète de la vidéo sur YouTube (p. ex., https://www.youtube.com/embed/TTzdcOcpyuE (https://www.youtube.com/embed/TTzdcOcpyuE))
2. Video Size (Taille de la vidéo)
   Saisissez la largeur et la hauteur de la vidéo (largeurxhauteur, sans espaces ; p. ex. 400x350).
3. Title (Titre)
   Saisissez le texte du titre, le premier morceau de texte à afficher juste sous la vidéo.
4. Subtitle 1 (Sous-titre 1)
   Saisissez le texte du sous-titre, qui s’affiche juste en dessous du titre.
5. Subtitle 2 (Sous-titre 2)
   Saisissez le texte du second sous-titre, qui s’affiche juste après le premier.
6. Show Banner after Top Reviews (Afficher la bannière après les meilleurs commentaires)
   Activez cette option si vous souhaitez afficher une bannière après la section vidéo des meilleurs commentaires.
7. Banner Image after Top Reviews (Image de bannière après les principaux commentaires)
   Si vous affichez la bannière, importez l’image (au format JPG) que vous aimeriez utiliser ici pour les écrans plus larges (taille d’image de 1800 pixels de large). Cette version sera utilisée pour les écrans d’une largeur supérieure ou égale à 768 pixels.
8. After Top Reviews Banner Mobile Image (Image de bannière mobile après les meilleurs commentaires)
   Si vous affichez la bannière, importez une image plus petite (au format JPG) que vous aimeriez utiliser ici pour les écrans mobiles (taille d’image de 1800 pixels de large). Cette version sera utilisée pour les écrans d’une largeur inférieure à 768 pixels.
   
   

Homepage - Tags (Page d’accueil - Balises)

Contrôle les paramètres pour la section des balises sur la page d’accueil.

1. Background Color (Couleur d’arrière-plan)
   Sélectionnez la couleur d’arrière-plan pour la section.
2. Label Color (Couleur du libellé)
   Sélectionnez la couleur du libellé « Tags » (Balises) dans la section.
   
   

Homepage - Social Plugins (Page d’accueil - Plugins sociaux)

Contrôle les plug-ins des médias sociaux affichés en bas de la page d’accueil.

1. Google Plus User ID (ID d’utilisateur Google Plus)
   Saisissez l’ID d’utilisateur de votre compte Google Plus pour afficher les activités récentes. Laissez vierge si vous ne souhaitez pas afficher ce plug-in.
2. Facebook URL (URL Facebook)
   URL de votre page Facebook pour charger le plug-in Facebook sur la page d’accueil. Laissez vierge si vous ne souhaitez pas afficher ce plug-in.
3. Twitter Timeline URL (URL du fil d’actualités Twitter)
   Your twitter URL page for timeline plugin to be displayed on homepage. Leave empty if you don’t want to display this plugin.
4. Twitter Timeline Widget ID (ID de widget du fil d’actualités Twitter)
   ID de widget pour le fil d’actualités de votre compte Twitter ; permet de charger le fil d’actualités dans la section de votre page d’accueil réservée aux plug-ins sociaux.
5. Twitter Username (Nom d’utilisateur Twitter)
   Nom d’utilisateur pour votre compte Twitter ; charge en même temps que le plug-in sur la page d’accueil. Il s’affiche en bas du plug-in.
6. Blog Logo (Mini) (Logo du blog (mini))
   S’affiche en bas du plug-in du blog. Format PNG recommandé avec arrière-plan transparent, 120 x 30 pixels.
   
   

Configurer de puplicites produit

Sur la page de consultation des produits de votre boutique en ligne, le thème Palisades vous permet d’afficher une image publicitaire d’un produit (sous l’image principale du produit, à gauche de la description). Pour utiliser cette fonctionnalité, vous devez a) activer le paramètre “Show Product Page Ad” (Afficher la pub de la page produit) et b) configurer et assigner des balises publicitaires aux produits en suivant les instructions ci-dessous.

Pour utiliser cette fonctionnalité publicitaire des pages produit, vous devez configurer les balises publicitaires des pages produit. Chaque balise que vous configurez est une publicité distincte qui inclut le nom du fichier d’image et un lien de redirection de l’utilisateur s’il clique sur une publicité donnée.

Pour créer une nouvelle publicité de page produit, commencez par importer le fichier d’image pour la publicité en accédant à SEOShop admin>>Tools (Outils)>>Files (Fichiers). Cliquez sur Upload Files (Importer des fichiers) et sélectionnez l’image que vous souhaitez utiliser pour la publicité. Il doit s’agir d’un format d’image web valide (PNG, JPG ou GIF), d’une taille recommandée de
370 x 370 pixels. Une fois le fichier importé, cliquez sur le texte de l’URL dans cette ligne des nouveaux fichiers et copiez la valeur de l’URL (CTL+C ou clic droit>>copier).

Maintenant que vous avez fourni un fichier d’image pour la publicité et que vous disposez d’une URL pour ce fichier d’image, l’étape suivante consiste à configurer la balise pour cette publicité produit. Dans SEOShop admin, accédez à Products (Produits)>>Tags (Balises), puis cliquez sur Add a tag (Ajouter une balise). En ce qui concerne la balise à utiliser pour la publicité de page produit, le titre de la balise doit être formaté exactement comme suit : ProductAd:nom_du_fichier_image=lien. Pour votre nouvelle balise, le titre commencerait donc par « ProductAd : », suivi de l’URL du fichier d’image que vous venez
d’importer (CTL+V ou clic droit>>coller pour coller l’URL que vous aviez précédemment copiée). Après le nom du fichier, vous devez saisir le signe « = », suivi de l’URL relative ou absolue de la destination vers laquelle vous souhaitez que redirige le lien.

Imaginez, par exemple, que vous souhaitiez utiliser une publicité produit. Vous importez donc le fichier d’image et obtenez l’URL vers un autre produit de votre site vers lequel vous souhaitez que le lien renvoie. Cela devrait donner ceci :

Nom du fichier d’image = //static.webshopapp.com/shops/132178/files/062965058/product-ad.jpg

URL du lien = /taylor-polytune-2-poly-chromatic-tuner.html

Avec ces informations, le titre de votre balise produit serait ProductAd://static.webshopapp.com/shops/132178/files/062965058/product-ad.jpg=taylor- polytune-2-poly-chromatic-tuner.html

Enfin, définissez le paramètre « Visibility » (Visibilité) de votre nouvelle balise produit sur « Visible » (de sorte que la balise soit disponible sur la boutique en ligne), puis cliquez sur « Save » (Enregistrer) pour créer la nouvelle balise.

Maintenant que vous avez configuré une balise de publicité produit, vous pouvez l’assigner à n’importe quel produit avec lequel vous souhaitez utiliser cette publicité en particulier. Pour ce faire, accédez à SEOShop admin>>Catalog (Catalogue)>>Products (Produits)>>select Product (Sélectionner un produit)>>Tags (Balises) et appliquez la balise de publicité produit que vous souhaitez utiliser. Une seule publicité produit peut être utilisée par produit. Donc si vous assignez plusieurs balises de publicité produit à un même produit, le thème n’utilisera que la première de la liste.

Notez que si elles sont configurées correctement comme indiqué plus haut, ces balises de publicité produit spéciales ne s’afficheront pas dans la section « Tags » (Balises) de la page de consultation du produit de votre boutique en ligne (car elles ne sont pas censées être vues par les utilisateurs).

Go to Top