One connected system for the entire device lifecycle.

No. Customers and contacts, carts and checkout, procurement and receiving, fulfillment, shipping and returns, assets, device management, and lifecycle operations run on one platform and share one data model.

Each login email belongs to one person across the platform, and a contact can hold several verified login emails with one marked primary. When a contact is added, Claddio matches on email, so a person who works with several organizations is linked to each one instead of being created again. New companies are checked against existing records by DUNS, Tax ID, name similarity, billing address, website domain, and phone, and possible duplicates wait in a review queue before any merge, which is audited.

One-time products in a specific condition and configuration, subscription products with their plan, billing term, trial, and setup fee, and services from the work-order service catalog. Any line can carry a price adjustment with an expiry date and an optional security deposit, and the cart can carry a free-shipping tier. Send it to one or more contacts as a checkout link or download it as a proposal PDF. At checkout it becomes an order, with the cart's owner and partner organization carried over.

During fulfillment, each serialized device is recorded against the order line it fulfills. That link carries through device management, returns, and reporting.

FedEx and UPS, through direct carrier integrations. Operations teams compare live rates, validate addresses, and create, print, or void labels from the fulfillment, with automatic tracking updates. Shipments can be billed to Claddio's account or a customer's or partner's own carrier account. USPS integration is in development while account setup is completed.

From the order in the customer portal. The customer requests a return as a refund, warranty, or repair, with a reason for the items being sent back. Once it is approved, the customer creates the carrier return label themselves. Operations receives and inspects each item, then resolves the return with a refund to the original payment method, account credit, replacement, exchange, or repair.

As each IMEI is entered against a purchase order, Claddio checks its TAC against an extensive, managed TAC database with reviewed model mappings. If the IMEI belongs to a different catalog item, receiving flags it and proposes the matched SKU, and the operator corrects it with one confirmation. IMEI 1 and IMEI 2 must identify the same model, and receiving cannot complete until every cellular IMEI passes. The same check runs on asset CSV imports and buybacks.

Yes. Claddio's operations team pays vendors directly from the purchase order once it is Confirmed, Partially Received, Received, or Closed Short. With Pay by Bank, the payment goes to the vendor's saved bank account after a review of the vendor amount, estimated fees, and total, and it reconciles against the purchase order automatically. Vendors add bank details through a secure, expiring link, entered with the payment provider and never stored by Claddio. Purchase orders paid at checkout, charged by the vendor, or paid outside Claddio are recorded on the same purchase order.

Claddio keeps track of which SIM is in which device, checks ICCID formats at intake, filters catalogs to devices compatible with a customer's network, and coordinates activations with partners and carrier teams through workflows.

Yes. Claddio is multi-tenant, with role-based permissions inside each organization and partner role templates that control which accounts each person can see.

Not yet. The automations canvas is in development. When it's released, workflows will be built visually from scheduled triggers, conditions, approval steps, sub-flows, and email templates, with no code required.

Dashboards and reports cover orders, finance and margin, commission activity, device posture and compliance, and activations.