Browse all

Aluleth Proposals Pro

Everything you need to set up Aluleth Proposals Pro: proposals and quotes your clients read, choose, sign and pay on one private page, with signed PDFs, several signers, follow-ups, what happens after signing, reports and AI drafts. Want to see it first? Open the live demo.

Contents

Requirements

  • WordPress 7.0 or newer and PHP 7.4 or newer. The PHP mbstring extension is not needed.
  • Copies bought on a marketplace (WPBay…) are complete: Aluleth Proposals 0.5.2 is included, nothing else to install and no licence key. Copies bought on the Aluleth Market are an add-on: they need the free Aluleth Proposals plugin (0.5.2 or newer), installed and active, and a licence key for the Pro features and updates.
  • Emails (the proposal link, codes, reminders, signed PDFs) are sent by your site’s own email setup (wp_mail). For reliable delivery, use an SMTP plugin, for example Aluleth SMTP.
  • Optional: WooCommerce or FluentCart for payments at signing (FluentCart for subscriptions and other currencies); Aluleth CRM, Boards, Membership and Forms for what happens after signing and quote requests; an AI provider connected in Settings › Connectors for AI drafts.

Installation

Marketplace copy (complete plugin)

  1. In your WordPress admin, go to Plugins › Add New › Upload Plugin.
  2. Choose the aluleth-proposals-pro-x.y.z.zip file as you downloaded it (do not unzip it), click Install Now, then Activate.
  3. Go to Aluleth › Proposals › Settings: company name, logo and colour, what is paid at signing and, with FluentCart, create the payment product.
  4. Click New proposal, choose a template, fill it in and send it.

If the separate Aluleth Proposals plugin is already active, leave it: Aluleth Proposals Pro uses it instead of its included copy, with your proposals and settings. It must be version 0.5.2 or newer. With an older version your proposals keep working, but the Pro features stay off and a notice asks you to update it; update it, or deactivate it and the included copy takes over with the same data.

Aluleth Market copy (add-on)

  1. Install and activate the free Aluleth Proposals plugin (0.5.2 or newer).
  2. Upload and activate Aluleth Proposals Pro.
  3. Enter your licence key in Aluleth › Settings › Licences.

Making and sending a proposal

  • Start from a template (website and shop, monthly retainer, consulting, event or photography, simple quote) or a blank page. Sections: cover, text, image, video link, team, pricing, timeline and terms, moved up and down.
  • Pricing tables with quantities, units, discounts and tax per line, in 30 currencies. A number for each proposal (your own format, with the year if you like) and an end date.
  • Send it by email with a private link, or copy the link. Changing a sent proposal makes a new version: the client sees the version you sent until you send the new one.
  • The client page is outside your theme, with your name, logo and colour, and is never indexed by search engines.

Pricing the client chooses (Pro)

  • Packages (the client chooses one line), optional lines (ticked or not at first) and quantities between the lowest and highest you allow.
  • Lines paid every month or year are shown apart (“Then $90 / month”) and are not in the amount due at signing.
  • What is signed is the proposal as the client chose it: the signed copy, the PDF and the fingerprint show exactly the lines taken.

Signing

  • The client draws their signature (mouse or finger) or types their name, and ticks that they agree to sign electronically. Or they decline and say why.
  • The record: who signed, their email, the time, the IP address, the browser, the version signed and a SHA-256 fingerprint of that content, in the signed PDF and in WordPress. “Check a PDF” tells you whether a file is exactly the signed copy kept on your site.
  • It is a simple electronic signature with a record of how it was given. Whether it meets the rules for your documents depends on your country: some documents need a handwritten, advanced or qualified signature. Check with a lawyer when in doubt.
  • Several signers (Pro): up to five people after the client, in order or not, each with their own link; your team countersigns last. A code sent by email checks each signer’s address (15 minutes, 5 tries). PDFs from your media library (a contract, your terms) can be signed with the proposal, each with its fingerprint.

Payments at signing (Pro)

  • Ask for nothing, a deposit (a percentage or an amount) or the full amount. Right after signing, the client pays on your shop’s checkout with its own payment methods: WooCommerce (“Pay for order” page) or FluentCart (a private “Proposal payment” product, created from the settings).
  • One order or cart is made per payment, also when the link is opened twice at once. A FluentCart order counts as the payment only when it holds the payment product alone, at the amount asked, in the proposal’s currency; anything else is noted on the proposal for you to check.
  • The payment shows as paid as soon as the shop says so. A full refund or a cancellation shows on the proposal; a partial refund stays in the shop. Bank transfer, cash on delivery and cheque count as paid once you mark the order completed.
  • Ask for the balance later, with the payment link emailed. Lines paid every month or year can start as a FluentCart subscription after signing.
  • FluentCart 2.1 with FluentCart Pro can take other currencies than the shop’s: a proposal in EUR in a USD shop is paid in EUR, at the exact amount.

Follow-ups and approval (Pro)

  • A reminder before the end date, and a short note (to the client or to you) when a proposal was opened but not signed after some days. Once per version sent, never after signing or declining; each proposal can turn them off. Each email is recorded before it is sent, so two tasks running at once never send it twice.
  • Proposals above an amount can be sent only once someone with access to Aluleth › Settings approved them. Any change (also a document or a signer added) asks for a new approval, and the approver approves the version they saw.

After signing (Pro)

  • Aluleth CRM Pro deal (opened when sent, won when signed, lost when declined or ended), tags on the contact, a project board in Aluleth Boards (with the client in the portal), a level of Aluleth Membership, an email with the client’s next steps, and a webhook to an https address.
  • Each step runs once on its own; the proposal shows how each went. A step that failed, or stopped half-way, runs again only when you click Run the steps left again: check first whether it was made.

Content library, reports and AI (Pro)

  • Save a section once (terms, a pricing table, the team) and add it to any proposal.
  • Reports for the last 30, 90 or 365 days: sent, opened, signed and paid, share signed, value signed, time to sign, by template and by person; and the seconds each part of a proposal is on screen during the client’s visits (no cookie).
  • AI drafts from a few lines, a quote request or CRM notes, through the AI provider connected in Settings › Connectors. Prices never come from the AI: it picks among the pricing tables of your library. “Rewrite with AI” on any text part. Nothing is sent before you press the button.

Where the signed PDFs are kept

Signed PDFs and documents are kept in a private folder of your uploads (wp-content/uploads/aluleth-proposals/, in a folder with a random name), each with a random name, and only sent by the plugin’s own pages after their checks.

The folder is closed with .htaccess (Apache, LiteSpeed) and web.config (IIS). Nginx does not read these files: the plugin checks every day whether a test file can be opened by its address and, if so, shows this rule on the Aluleth screens, for your host to add to the site’s Nginx configuration:

location ^~ /wp-content/uploads/aluleth-proposals/ { deny all; }

Or keep the files outside your website: add define( 'ALULETH_PROPOSALS_FILES_DIR', '/path/outside/the/website' ); to wp-config.php. New files go there, and the files saved before move there with the daily task. If the folder cannot be used, a notice on the Aluleth screens says so and the files stay where they are.

Privacy

  • Proposals, signatures, payments and the time read stay in your WordPress database; signed PDFs in the private folder above. Nothing is sent to us.
  • Visits are counted without cookies: a counter under a salted hash of the IP address and browser is kept for half an hour, then deleted by the daily clean-up.
  • Tools › Export Personal Data and Erase Personal Data cover proposals, questions, signatures, payments and time read, page by page. Signed proposals are kept with their signature as the record of the agreement. A suggested text for your privacy policy is in Settings › Privacy › Policy guide.
  • Outside services, only when you use them: your AI provider (AI drafts and rewrites), the webhook address you set, and Frankfurter reference rates (FluentCart in another currency, only the two currency codes). The readme lists what is sent and the terms and privacy links.

Translating the plugin

  • aluleth-proposals (template aluleth-proposals.pot; in the marketplace copy it is in free/languages/ inside Aluleth Proposals Pro) covers the proposals, the client page, signing and the PDF.
  • aluleth-proposals-pro (template languages/aluleth-proposals-pro.pot) covers the Pro features and the shared Aluleth screens.
  • Put the .mo files in wp-content/languages/plugins/: they are kept when the plugin is updated.

Uninstalling

Deactivating keeps everything. Deleting the plugin removes the proposals, signatures, signed PDFs, payments and settings only when you ticked it in Aluleth › Settings; the licence, scheduled tasks, locks and short-lived records always go. With a marketplace copy, the data is kept while the separate Aluleth Proposals plugin is still installed. Private FluentCart products used for payments are kept (orders point to them).

Troubleshooting

  • Emails do not arrive. Use an SMTP plugin (for example Aluleth SMTP). Reminders run with WP-Cron: on a site with few visits, set up a real cron job.
  • A notice says the signed PDFs folder can be opened. Add the Nginx rule above, or set ALULETH_PROPOSALS_FILES_DIR.
  • The client cannot pay online. Check that WooCommerce or FluentCart is active and takes the proposal’s currency, and, with FluentCart, that the payment product was created in the settings.
  • The Pro features do not show. If the separate Aluleth Proposals plugin is active, it must be 0.5.2 or newer. For a copy from the Aluleth Market, check the licence in Aluleth › Settings › Licences.
  • Still stuck? Contact support through the place where you bought the plugin, with your WordPress, PHP and plugin versions.