An online store that works with your back office.

01

A web store and mobile apps built around your brand

Your business stays in front: your store name, logo, colours and domain on the web, with a separately branded shopping app for iOS and Android. Customers browse your products and place orders with your business rather than shopping inside a shared marketplace.

The website and apps share the same store connection. Your team manages the underlying catalogue and online ordering settings in Tellency instead of maintaining a separate product list for each channel. Start with a website, add apps, or plan the channels together.

02

From product discovery to collection or delivery

Customers can explore categories, search products, view product photos, choose quantities and build a cart. Delivery and pickup options, minimum orders, delivery fees and available time slots follow the store configuration.

Order tracking follows progress through acceptance, packing, delivery or pickup and completion. The business handles the work in Tellency, keeping the customer-facing order connected to the operational record.

• Product categories, search, offers and product details.
• Cart, quantity choices and product notes, including supported weight-based items.
• Configured delivery or branch pickup, fees and time slots.
• Customer order history and order progress.

03

Online orders belong in the ERP workflow

Tellency is the operating system behind the store. Decide which products and categories are sold online, choose the fulfilment branch and manage incoming orders. The checkout validates and prices the order on the server.

When an online order is completed, the configured workflow records its sales invoice and payment and moves stock from the fulfilment branch. Your implementation walkthrough should include the full order lifecycle, a cancellation and a stock or price change—not just a storefront tour.

04

AI-native tools for the work behind the storefront

Authorised Tellency agents can use supported storefront tools to inspect settings, look up products, update online availability, manage product photos and progress orders. These are business actions tied to permissions and execution records.

Use a representative request in the demo: find an open order, check its state and carry out an allowed next step. Confirm the enabled tools and approval rules for your team. The shopper experience and the permissions given to an operational agent are configured separately.

05

Choose a launch that fits how you trade

Bring your product types, branch locations, delivery area, expected order workflow and branding. We scope the web store, app builds, deployment, training and ongoing support around that operating model.

For businesses serving the US, Canada, Asia or MENA, confirm the required currency, address formats, account verification, payment collection and customer communications during discovery. App distribution, store accounts and any gateway or third-party connection are agreed in the proposal.

Ecommerce questions, answered

01

Make your catalogue easy to explore

Give shoppers category pages, product search and product details with photos, prices and availability. Organise the published assortment around the way customers shop, while keeping the underlying product records in the ERP.

Online selling is controlled by product and category settings. Your team can decide what belongs in the storefront rather than publishing the entire ERP catalogue by default. Product images and descriptions deserve the same attention as stock and price accuracy.

02

Build the checkout around your store rules

A customer chooses delivery or pickup from the options enabled for the store. Minimum order values, delivery fees, free-delivery thresholds and time slots help communicate the service before the order is placed.

For pickup, identify the available branch and collection window. For delivery, configure the area, fees and fulfilment branch. Test an address that cannot be served, a changed cart and a slot that no longer works so the customer knows what to do next.

03

Give customers a route back to their order

The storefront includes order lookup and progress, with customer account and order-history flows available in the current code. Account sign-in methods and messaging services are configured for the deployment.

The public order journey should explain whether the order is accepted, packed, ready for pickup, out for delivery or complete. Agree the team responsible for each step so the status shown to the customer reflects the work happening in the branch.

04

A website foundation that search engines can read

The storefront renders product and category pages on the server and includes metadata, a sitemap and product structured data. These features make product information accessible to crawlers and provide a foundation for ecommerce SEO.

Your catalogue content still matters: clear titles, useful descriptions, original images and accurate pricing and availability. Domain setup, crawl checks, content quality and product data should be part of launch acceptance. Technical markup makes pages eligible to be understood; it does not guarantee indexing or a search position.

05

Extend to an app when there is a clear customer use case

A web store gives first-time shoppers a link they can open immediately. If repeat customers would benefit from an installed shopping experience, Tellency’s branded iOS and Android apps can use the same store connection.

Keep the catalogue and order workflow consistent as channels expand. Agree any additional design, payment provider, shipping connection or regional requirement in the project scope.

Ecommerce questions, answered

01

A shopping app with your own identity

Each client can have a separate app name, iOS bundle identifier and Android package identity. App icons, brand colours, splash presentation and the store logo are configured for that client’s build.

This is a customer shopping app, distinct from the mobile tools used by staff to operate the ERP. Its purpose is to help your customers browse your catalogue, place orders and follow their progress under your brand.

02

A complete browse-to-order journey

Shoppers can browse aisles, search the catalogue, open product details and add items to their cart. Product photos, offer prices, quantities and supported weight selections help customers choose before checkout.

The cart shows the relevant minimum order and delivery rules. At checkout, customers provide their details, choose delivery or pickup and an available slot, and select a supported payment collection method. Order history and progress help them return to the purchase after placing it.

• Home, categories and product search.
• Product photos, details, quantities and cart.
• Delivery or pickup checkout with configured slots.
• Account, order history and order-tracking screens.

03

The same store connection as your website

The app connects to the client’s storefront service, which connects to Tellency ERP. Catalogue and order operations therefore follow the same store setup as the web channel.

The ERP credential stays on the server rather than being shipped inside the customer app. The implementation should also verify sign-in, session handling, address formats and failure recovery on both iOS and Android.

04

Plan app distribution as part of the rollout

Agree the app display name, store listing content, artwork, identifiers and the developer accounts used for distribution. Client approval, build signing, submission and store review are separate milestones in the launch plan.

Use a pilot with real devices to check readability, permissions, checkout and order tracking. Public App Store and Google Play availability depends on the individual client release and platform review; a branded build is not a promise of an already-published listing.

05

Add mobile because the customer journey calls for it

An installed app can make sense for customers who order repeatedly and want a familiar route back to the store. Keep the website available for new customers, search discovery and links shared by your team.

Scope any additional mobile capability, such as push messaging or a new online payment provider, explicitly. Start with the shopping and fulfilment experience you can demonstrate and support.

Ecommerce questions, answered

01

What white-label means for your business

The customer-facing experience uses your store name, logo and brand colours. The website runs on your domain; iOS and Android builds can carry your app name, icon and client-specific application identifiers.

The shared platform provides the shopping and ERP workflows underneath. Agree the branding, custom functionality, ownership and ongoing maintenance in the proposal so your team has a clear plan for launch and future releases.

02

Decide the identity before the first build

Prepare the brand name as it should appear on the home screen, approved icon artwork, the storefront domain and the customer support details. Confirm who controls the domain and the developer accounts used for the mobile release.

Tellency supports per-client build configuration for the app name, icon, colours, splash presentation, iOS identifier and Android package. Store name, catalogue and operating rules come from the connected store.

• Approved logo, colours, app icon and display name.
• Your storefront domain and customer support information.
• iOS and Android app identities and distribution-account responsibilities.
• Agreed store listing copy, screenshots, policies and launch approvals.

03

Keep the brand and the fulfilment promise aligned

Branding is only part of the experience. A delivery promise in an app needs an available branch, realistic time slots and a team that accepts and packs orders. The configured delivery and pickup rules should match what the store can actually provide.

Tellency connects the published catalogue to incoming orders and the fulfilment process. Demonstrate the same order in the branded storefront, the app and the ERP so the customer-facing messages line up with operational status.

04

Scope the launch and ongoing ownership

A proposal should identify the website deployment, mobile builds, branding work, content preparation, account setup, testing and support. It should also name the owner of app updates, signing credentials, store-review responses and customer service.

Any additional payment gateway, logistics provider or custom capability needs a defined scope and acceptance criteria. Agree the ongoing maintenance and release process so the branded experience stays usable when mobile operating systems or business requirements change.

05

Use your own operating scenario in the walkthrough

Bring a product assortment, a customer order and a fulfilment branch. Ask to see how catalogue publication, checkout, order tracking, invoice creation and stock movement connect.

We can then plan whether to launch the website first, release apps alongside it or run a smaller pilot. The timeline and commercial terms follow the agreed scope rather than a generic package promise.

Ecommerce questions, answered