Square vs iPad POS: A Verification Guide for Specialty Retail

Start With the Current Offers

POS packaging, hardware, processing, and feature availability change. Before comparing platforms, open each vendor's current pricing and product documentation and record the exact plan, device, payment path, location count, and add-ons being quoted. This guide deliberately does not freeze Square pricing or packaging into a claim that may become stale.

Tillr's current public offer is:

• Core software is $0/month after you complete Tillr Pay onboarding and one successful Tillr Pay payment by day 14.
• Payment processing fees apply.
• Payment hardware, shipping, replacements, custom migration, implementation, and enterprise rollout work may cost extra.
• Tillr Pay onboarding and payment acceptance remain subject to underwriting and applicable payment terms.

Compare One Real Store Workflow

A useful evaluation follows the same sale through both systems:

1. Find or scan an item from a representative catalog.
2. Add the right customer and loyalty context.
3. Apply the discount, tax, prompt, or manager action the store actually uses.
4. Complete the intended tender on the intended device.
5. Confirm the receipt, transaction record, and stock effect.
6. Review how the same item appears online and in reporting where those channels are enabled.

Record what worked, what required another plan or add-on, and what needs configuration or manual follow-up.

Catalog and Inventory

Bring a sample that includes duplicate SKUs, duplicate barcodes, categories, brands, tax assignments, inactive items, online visibility, and any parent-child or matrix data from the current system.

Tillr supports item-level catalog and stock workflows, bulk operations, low-stock tools, and reviewed CSV/XLSX migration. First-class variant grouping is not available yet. Do not choose Tillr on an assumption that size/color matrices will import or operate as mature variants; inspect how every source row will be represented.

For Square, verify the current plan and documentation against the same sample rather than relying on a third-party feature list.

Checkout and Payments

Test search, barcode scanning, saved layouts, customer lookup, discounts, refunds, manager controls, receipts, and the intended Tillr Pay option. Payment support depends on completed onboarding, the configured payment path, supported hardware, and connectivity.

Run the same checklist against the current Square setup and quote. Avoid calling either product "faster" without a repeatable test using the store's real catalog and device.

Loyalty and Customer Workflows

Compare enrollment, customer lookup, points or reward rules, redemption, returns, consent, and reporting. In Tillr, customer and loyalty tools are part of eligible core software. Confirm the exact Square plan or add-on required for the workflow being evaluated.

Offline and Recovery

"Offline" is not one universal capability. Test which catalog, cart, cash, card, receipt, customer, and synchronization actions remain available on the planned device and payment setup. Then reconnect and verify that queued work is visible, deduplicated, and reconciled.

Tillr's offline behavior varies by device and payment path. Some workflows require connectivity, and card acceptance depends on the configured provider and hardware. Ask Square the same workflow-by-workflow questions using its current documentation.

Migration

Tillr can review recognized product exports and generic CSV/XLSX files. The safe path preserves the source file, previews mapping, surfaces conflicts, validates a sample, and requires manager approval before committing the selected-store catalog. Parent-child rows, images, taxes, and source-specific fields may require manual cleanup, and there is no universal migration duration or merchant-facing rollback promise.

For Square exports, follow Square's current first-party instructions. Export formats and dashboard navigation can change.

Make the Decision From Evidence

Choose the platform that best matches the validated catalog, checkout, payment, channel, hardware, support, and rollout requirements. Keep screenshots or notes from the exact plans reviewed, and make every important claim prove itself in the same representative store workflow before committing.