File compatibility requirements for mSeller

Modified on Mon, 18 Mar 2024 at 04:20 PM

Banner - This image forms the large background graphic you see on the dashboard. The file format needs to be .png and must be named ‘banner’. To show a selection of banners, add sequential numbers to the file name. E.g. banner.png, banner_1.png, banner_2.png. These can then be scrolled through on your dashboard. The optimum dimensions are- 1546x1136 or a similar ratio. These images need to be supplied to us directly.

Dashboard - This image sits below the main banner. It also needs to be in .png or .jpg format and named ‘dashboard’ e.g. dashboard.jpg. You cannot add multiple of these. The optimum dimensions are – 1546x173 or a similar ratio. This image needs to be supplied to us directly.

Product Photos – Must be named exactly as the product code, with .jpg as the suffix, e.g. AA11.jpg (where AA11 = product code). The optimum dimensions are 600x620 or a similar ratio.

Items with ‘/’ in product code - Because files cannot be named with a ‘/’ symbol, this character must be replaced with a hyphen (‘-‘) in the image name e.g. ‘abc/123’ will be ‘abc-123.jpg’.

Additional Images - can also be supplied per product, but must be named with a tilde (~) suffix, followed by an index number e.g. abc123~1.jpg. abc123~2.jpg etc to be recognized by the app. Category and sub-category Photos can be supplied to represent a whole product group or sub-group. The dimensions for optimum display should be 154x126. The file should be named.jpg, e.g.Clothes.jpg.

Extragroup Photos – This refers to the ‘Tagging’ of products that you wish to group under a temporary or seasonal event e.g ‘Back to School’, ‘Clearance Items’, or ‘Christmas Stocking Fillers’. The name on the file needs to match the name of the extra group precisely, or it won’t appear on your mSeller app properly. You will also need to incorporate the name of the grouping in the graphics supplied. These pictures need to be 500x400 or a similar ratio.

Associated product Files – only 1 type of each file format can be added per product. File names should be eg, AA11.pdf , AA11.doc –AA11.xls. The exception is images, of which you can have multiple per product.

Video – a file can be supplied and associated per product. Mp4, .M4v, .Mov file types can be used (max 1 per product). File naming should take the format: eg AA11.mov etc.

TEXT FILES - The system supervisor has the ability to create text files that can be placed into the relevant reps' iPad directories.
1) Teamtalk – to get sales messages, alert messages, promotions, or any other messages to the mSeller user, create a text file called infoDDMMYY_HHMM.txt (‘info’ followed by date and time). Please note that this text document must be named in the exact format as included above to function correctly. In the text document, the first line is used for the title of the message e.g. Discount on summer items, and any line below is for the contents of the message. To transfer these messages to mSeller users, place these text documents in the ‘New’ folder within the photo directory in use for SOP. Then use the proto processing tool, included in ‘Photo Processing.docx’. Ensure that the ‘validate’ checkbox is unticked when processing text documents. Once these text files have finished processing in SOP, in mSeller, a ‘Part Update’ will receive these messages.

2) Item notes - In order to provide each user with a dropdown list of selectable messages per order item, create a text file called Lnotes.txt. Use a message name and then a comma to separate the title from the message, eg:

Price1, price requested for this order only

Price2, price requested for all orders

Green, no green ones, please.

Place each message on a new line. To transfer these messages to mSeller users, place these text documents in the ‘New’ folder within the photo directory in use for SOP. Then use the proto processing tool, included in ‘Photo Processing.docx’. Ensure that the ‘validate’ checkbox is unticked when processing text documents. Once these text files have finished processing in SOP, in mSeller, a ‘Part Update’ will receive these messages.

3) Order notes - In order to provide each user with a pre-defined dropdown list of selectable messages relating to the whole order, create a text file called onotes.txt. Type separate messages on each line. e.g.

Tail-lift required Pack in mail-order boxes

Price labels required

To transfer these messages to mSeller users, place these text documents in the ‘New’ folder within the photo directory in use for SOP. Then use the proto processing tool, included in ‘Photo Processing.docx’. Ensure that the ‘validate’ checkbox is unticked when processing text documents. Once these text files have finished processing in SOP, in mSeller, a ‘Part Update’ will receive these messages.

4) Call log notes - This file should be populated with a single line entry for each pre-defined call-log note that you want the rep to be able to select at the end of the call log. Create a text file called Cnotes.txt. To transfer these messages to mSeller users, place these text documents in the ‘New’ folder within the photo directory in use for SOP. Then use the proto processing tool, included in ‘Photo Processing.docx’. Ensure that the ‘validate’ checkbox is unticked when processing text documents. Once these text files have finished processing in SOP, in mSeller, a ‘Part Update’ will receive these messages.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article