Px Mailer is built to be extended. If you can write useful Python plugins, you can package them, document them, and sell them to Px Mailer users — or offer custom plugin work as a service. This post explains two things:

      • How plugins work in Px Mailer (full practical guide)
      • How creators can make money by building and selling plugins around the Px Toolx ecosystem

1. Why plugins are a real business opportunity

      • Many users want custom sending logic, name generators, template packs, lead loaders, or API bridges
      • Not every customer wants to code — they will pay for a ready plugin + setup help
      • One good plugin can be sold many times as a digital product
      • Custom plugin freelancing can become recurring support income
      • Plugins sit next to Px Mailer, so buyers already understand the host product

2. #TERMS — selling plugins the right way

Before you sell anything, follow these terms carefully:

      • Own your work — sell only plugins you created, or have clear rights to sell
      • Do not steal — do not copy another creator’s plugin code, branding, or docs and resell them as yours
      • Be honest — describe exactly what the plugin does, what license level it needs, and what it does not do
      • No malware — plugins must not steal data, hide backdoors, or harm buyers’ systems
      • Respect Px Mailer licensing — your plugin does not replace a valid Px Mailer license; buyers still need Px Mailer
      • Support clarity — say whether you offer install help, updates, or refunds
      • Legal use only — buyers must use plugins for lawful email and business purposes
      • Px Toolx payout rules — if you want to be paid through Px Toolx creator/reseller channels, follow the current official terms on https://pxtoolx.com

3. Full explanation — how plugins work in Px Mailer

3.1 Where plugins live

      • Open your Px Mailer data folder
      • Go into the pxmailer folder
      • Open the plugins folder (create it if missing)
      • Path looks like: Px Mailer/pxmailer/plugins/
      • Each plugin is normally a Python file, for example my_helper.py

3.2 How to enable a plugin

      • GUI: Settings → Plugins & Variables
      • Add a line like: [USE my_helper]
      • Save Settings — Px Mailer reloads plugins
      • Manual: edit pxmailer/config.ini and add [USE my_helper] on its own line
      • The module name must match the file name: my_helper.py → [USE my_helper]

3.3 How users call your plugin from a message

Simple helper plugins expose functions. Users call them from message.txt, subject, or sender fields using Px Mailer sudo expressions. Example with the included sender_name style plugin:

      • Enable: [USE sender_name]
      • In a template, call a method through NewModule['sender_name'] inside Px Mailer sudo braces
      • Example methods: generate_security_name(), generate_order_name(), generate_shipping_name()
      • Px Mailer evaluates the expression per lead while building the email

3.4 Content-pack style plugins

      • Some plugins provide rotating subjects/HTML through get_px_internal_mail_content()
      • Examples in the ecosystem: TemplatePack and TemplateGenerator
      • These can return subject, html, and optional attach_path
      • Px Mailer can prepend plugin HTML and use plugin subject material during send
      • If you sell a template pack, include clear install notes for any data files (for example .pxb assets)

3.5 Mode 7 Private API plugins (Send_API)

      • For custom send transport, buyers use send mode 7 (Private API)
      • They need a plugin named Send_API enabled with [USE Send_API]
      • Your Send_API plugin must be callable and expose a send() method used by the campaign engine
      • Mode 7 is often license-gated above Standard — tell buyers that clearly
      • Document required inputs, API keys, and rate limits in your sales page

3.6 Custom variables

      • Users can also define [VAR name = expression] in Plugins & Variables
      • Variables can call your plugin helpers after the module is loaded
      • Teach buyers one clean example in your README

4. How to build a plugin people will buy

      • Solve one clear problem — example: better sender names, CRM lead import, custom API send, template pack
      • Keep install simple — one .py file + one [USE] line when possible
      • Ship a README — enable steps, example template lines, requirements, license notes
      • Include a demo — short screen recording or sample output
      • Version your plugin — v1.0, v1.1 so buyers know what they purchased
      • Test on a clean Px Mailer install before selling

5. What to put in your plugin package

      • The .py plugin file
      • Optional data files your plugin needs
      • README with install + usage examples
      • Changelog
      • Support contact / update policy
      • License terms for the buyer (personal use, agency use, redistribution rules)

6. How to sell it

      • List it as a digital product on your own site or through Px Toolx channels if available
      • Price by value: simple helper vs full Send_API integration vs ongoing support
      • Offer a basic version and a Pro version with setup help
      • Use prepaid credits / reseller options on https://pxtoolx.com when that fits your model
      • Upsell: custom modifications, private builds, monthly maintenance

7. Delivery and support workflow

      • After payment, send the plugin zip + README
      • Ask for their Px Mailer version if support is included
      • Help them add [USE YourPlugin] and test with 1–2 leads
      • Keep a private copy of each sold version for re-delivery

8. Creator quality checklist

      • Works after a fresh [USE] enable
      • Fails politely with clear errors
      • Does not overwrite unrelated user files
      • Docs are understandable by non-developers
      • No hidden network calls the buyer did not agree to

9. Bottom line

Px Mailer’s plugin system is a product platform. Learn the [USE] flow, ship something useful, document it clearly, and sell it honestly under the terms above. Start here: https://pxtoolx.com