Choose a SendURL plan around the job your links need to do

A launch team asks which plan it needs before it knows how many routes will remain in circulation or when the report will be reviewed. Start with those jobs. A plan comparison becomes easier when each paid feature has a concrete reason to be required rather than a vague promise of better marketing.

Count the inventory you will retain

SendURL’s link limits concern the organization’s saved inventory. Free supports 25 tracked links; Pro supports 1,000; higher tiers have larger limits. Do not model this as a fresh creation allowance every month.

Deleted links retain their slug and still count toward the link limit. A campaign process that assumes old routes can be deleted to reclaim capacity will make the wrong plan calculation. Use deliberate reuse where the reporting question permits combined activity, and separate routes where the distinction has a real purpose.

Match history to the review date

Free’s dashboard history is seven days. Pro provides 90, Premium 180, Team 365 and Enterprise the long catalogue window marketed as Lifetime. Choose the reporting cadence before promising a later date-scoped review.

A link’s supported all-time API statistics are not interchangeable with the dashboard’s selected date window. Likewise, a longer history does not create missing purchases or registrations. Keep the business outcome in its own system and define how the link report will support that question.

Decide whether destinations must change later

Creating a new approved destination route is available across plans within the applicable limits. Editing an existing saved destination after creation is Pro+, including UTM query changes. This is often the decisive capability for a long-lived printed address or a maintained profile slot.

For an illustrative care card, the team expects a documentation move after packaging is printed. A maintained short route can keep its public address while the approved target changes on Pro+. It cannot change the hostname or characters already printed on the card, so ownership and artwork continuity still matter.

Separate advanced measures from outcomes

Approximate unique visitors, cities and UTM statistics are Pro+ advanced analytics. These can answer useful reporting questions under their definitions. They do not identify named customers, certify location or create native revenue attribution.

A locked value on Free is not a measured zero. If the report genuinely requires an advanced dimension, plan for that entitlement. If the actual task is only verifying the correct route and reading recorded requests, do not invent a need for a more elaborate metric.

Check the QR requirement precisely

Free organization QR codes carry the SendURL mark and allow one styled-QR link. Pro+ removes the mark and allows styling across links. That is different from the earlier inaccurate claim that Free has only a plain code and every style requires Pro.

QR styling is self-serve (colours, dot and corner shapes; Free on one link, paid plans on every link), and no plan offers a logo-upload control. A plan change also does not repaint exported artwork or an already printed box. Retain proof and maintenance responsibilities regardless of the tier chosen.

Consider other allowances independently

Free has five tags, one link with a custom preview and one running A/B test with two variants. Paid plans allow unlimited tags, previews and tests, with up to four A/B variants. Free’s test retains the stored destination as a variant receiving at least half the weight; changing the stored destination through Pick winner is Pro+.

Free also includes one custom domain and one snu.to subdomain. Domain setup availability and active serving status are separate from the numeric allowance. Check the current product surface or support process rather than assuming the count guarantees immediate setup.

Use the price table for the actual capacity decision

These are the current SendURL catalogue prices and capacities; review pricing and the checkout terms at purchase. Every paid tier is self-serve through Paddle. Extra seats and support reply times are arranged by hand on request rather than provisioned in the dashboard.

Make the smallest sufficient decision

Write down the required route count, review window and controls, then choose the plan that fits them. A higher tier should solve an identified capacity or feature need, not substitute for an unapproved destination or an undefined conversion outcome.

Create an owned SendURL account when the workflow is ready. The feature tour explains the surfaces, and the API reference specifies supported integration behavior. Keep plan capability, route maintenance and business evidence as separate parts of the decision.