Add to Favourites

Tally Marketplace Publisher Guidelines

Naming, publishing, pricing and support guidelines for your solutions

These guidelines bring together everything you need to follow when you publish a solution on Tally Marketplace. Following them helps customers find your solution, trust what they are buying and get help when they need it. For step-by-step instructions, refer to the Creating a TCP File and How to Upload a Solution guides.

1. Publisher identity

Your publisher name is how customers recognise you across every solution you list.

• Use your registered company name, exactly as it appears in your Tally Developer Hub account, for example TK Solutions Pvt Ltd.
• Use the same name everywhere: in the Author field of Build Options and across all your solutions and releases.
• Avoid nicknames or changing names.

2. Solution name and listing title

The solution name is the first thing a customer reads. It should tell them what the solution does in a few words.

• Describe the outcome, not the technology. “GST Invoice Print with QR Code” tells a customer more than “TK Print Project 2”.
• Keep it short. Aim for 3 to 6 words and stay within 50 characters.
• Use Title Case. No ALL CAPS, emojis or decorative symbols like ™ or !!!
• Do not start the name with “Tally” or use it in a way that suggests an official Tally product. “Payroll Reports for TallyPrime” is fine; “Tally Payroll Pro” is not.
• No version numbers, superlatives or price claims such as “v2”, “Best”, “No. 1”, “Cheapest” or “Free”.
• No keyword stuffing. Use the description and keywords fields for search terms.
• Make it unique. Search Tally Marketplace before you upload and add a distinguishing word if a similar name exists.
• Match the name inside TallyPrime. The listing title should be the same as the Name field in your solution’s Build Options.

3. File naming

Every file in your submission follows one pattern, so reviewers and customers can tell at a glance which solution and version it belongs to.

Pattern: PublisherInitialsSolutionNameFileTypeVersion.extension

• Use only letters and numbers. The only dot allowed is the one before the file extension.
• Capitalise the first letter of each word, for example TKSafetyPolicyTracker.
• Use the same base name and spelling for every file in the submission.
• Add the version to versioned files (solution file and user guide) as a lowercase “v” followed by the digits without dots, for example v120 for 1.2.0.
• Keep file names under 60 characters.
• Number screenshots in display order with a short description of what each one shows.

4. Versioning

Every update you upload gets a new version number, so you and your customers always know which build is installed.

Use Major.Minor.Patch, starting at 1.0.0 for your first upload.

• Keep the version identical in three places: the Version field in Build Options, the file names and the version on the listing.
• Never re-upload a changed file with the same version. Even a one-line fix gets a new patch number.
• Never reuse or go backwards. If 1.3.0 had a problem, fix it in 1.3.1.
• When you reset lower parts, reset to zero.4.2 moves to 1.5.0 or 2.0.0, not 1.5.2.

5. Building the TCP file

Your solution file must meet these requirements to be validated on upload.

• A valid TPD license is required to create a TCP file.
• TCP Format must be set to Inscribed V2.
• Do not select Authorization Required.
• Name, Author and Version in Build Options must match your listing title, publisher name and listing version.
• Keep the GUID the same when you update an existing solution. A new GUID is treated as a different solution.

6. Listing content

A complete, clear listing helps customers understand your solution and decide to buy it.

Mandatory files

• TCP file, User Manual and Logo are mandatory.
• Supporting files, presentation, screenshots and developer manual are optional but recommended.

Descriptions and highlights

• Short Description: a one or two line summary that tells customers what the solution does.
• Full Description: explain what the solution does, who it is for and how it works.
• Highlights: up to five short points that tell customers why they should use the solution.
• AI assistance: you can use AI Generate for descriptions and highlights. Always review and edit the output before you accept it.

Screenshots and video

• Show the solution inside TallyPrime, in the order a customer would use it.
• Add a short demo video as a YouTube link. A larger solution with several screens may need more screenshots and a longer video.

The Sample Listing Content document shows a complete example of descriptions and highlights.
Click here to Download – Marketplace Sample TDL 

7. Discoverability

These help customers find your solution when they search or browse Tally Marketplace.

• Add relevant keywords, separated by commas, such as the feature, report or industry your solution serves.
• Choose the correct Category, Solution Type and Industry.
• Set compatibility accurately: Education Mode, Product Types, Editions and the TallyPrime Release range.
• Keep your solution updated with the latest TallyPrime release. Test it on each new release, update the supported release range and publish an update if needed.

8. Pricing

There are no platform price restrictions. Price your solution based on its value.

• Select Paid as the Pricing Model.
• Enter the Silver edition base price, regardless of your Product Type selection.
• Enter the price in INR or USD depending on your edition. If your edition is set to All, you can enter INR and USD prices separately.
• Gold pricing is automatically calculated as 3x the Silver price, and subscription pricing is automatically set at 20% of the purchase price.
• Review the Final Pricing Summary carefully before you confirm.
• Trial: you can enable an evaluation period and select the number of days.
• Price changes: currently, you can change the price 24 hours after your solution is published. This may change, so keep an eye on the help documents.

Commercials: The baseline commercials are 45% for the developer and 35% for the Seller Partner. However, keep an eye on the different campaigns and drives from Tally for the latest applicable commercials.

9. Publishing and updates

• Validate the TCP file after you upload it. The GUID and Version are read from the file and locked.
• Publish: once you confirm the pricing summary, your solution is published to the Marketplace.
• Updates: from Marketplace → Manage, upload the new TCP file with a higher version number and the same GUID. Update the user guide and screenshots if anything has changed.
• Unpublishing: you can remove a solution from Marketplace → Manage.

TallyShop Partners: All TallyShop add-ons will be migrated when the Developer Portal launches. TallyShop will keep working until Tally Marketplace is launched. If you make changes to your add-ons on TallyShop during this period, you will need to make the same changes separately on the Developer Portal.

10. Customer support

Customers can raise a support ticket from Tally Marketplace. You can see and respond to these tickets from the Support section of the Developer Portal.

• Check the Support section regularly and respond to tickets within 24 hours.
• Keep your User Manual complete and current, so customers can set up and use the solution without raising a ticket.
• When you fix a reported issue, publish it as a new patch version, so the customer can confirm which build has the fix.

Checklist before you publish

• Publisher name matches your registered company name and is the same across all your solutions.
• Listing title is 3 to 6 words, within 50 characters, in Title Case, with no version, superlatives or misuse of “Tally”.
• Listing title matches the Name field in Build Options.
• TCP file is built in Inscribed V2 format, without Authorization Required.
• For an update, the GUID is the same and the version is higher than the last upload.
• Version is the same in Build Options, file names and the listing.
• Every file name uses only letters and numbers, follows InitialsSolutionNameFileTypeVersion, and uses the same spelling.
• TCP file, User Manual and Logo are attached; screenshots are numbered in display order.
• Short Description, Full Description and Highlights are reviewed, and keywords, category and industry are set.
• Compatibility and the TallyPrime Release range are accurate.
• Prices in the Final Pricing Summary are correct.