Taxi and private hire

Cordic customisation: what you can change.

Start by checking how your office opens Cordic. If a booking or administration screen is a normal page in Chrome, you can explore clearer labels and lists there. An installed Cordic dispatch window cannot be changed by a Chrome extension.

No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.

Ideas to try

Small requests for a clearer working day

Start with information already visible on your page. These examples are possible requests; check the result in the preview before keeping it.

  • 01

    On this web booking list, make pickup and return times easier to distinguish

    Give each displayed time a clearer label and visual separation.

  • 02

    Make the contract reference stand out on this browser page

    Find the reference already shown when handling an account enquiry.

  • 03

    Add more space between rows in this web administration table

    Reduce visual crowding when checking bookings at the desk.

  • 04

    Keep the headings visible in this browser-based booking report

    Read long tables without losing the meaning of each column.

Ready-made changes related to these ideas

These general browser tools use the page elements your software exposes. Read their requirements and preview them on a suitable screen.

Custom Cordic screens, automations or a developer?

The right approach depends on what you want to change. Use Cordic settings for features the product already provides, and Tweaksy for small changes on an accessible browser page.

Browser customisation

Modify the screen you work with

A request such as “On this web booking list, make pickup and return times easier to distinguish” starts with information already visible. Tweaksy builds the change on that page for you to preview, then you can approve it for matching screens on your account.

Workflow automation

Know what needs the platform

Cordic automations that allocate jobs, process bookings or exchange data with a partner belong to Cordic's operational platform. Tweaksy's examples here only change the presentation of a browser page, such as making a visible contract reference easier to read. They do not run dispatch workflows.

Developer work

Connect systems or add new capabilities

For a custom Cordic integration, first speak to Cordic about the interfaces available for your installation and the system you want to connect. A developer needs that confirmed scope. For visual changes, establish that the particular screen is an ordinary Chrome page before considering Tweaksy.

Explore Cordic's official options ↗

A small change, ready for your team

  1. Choose one screen

    Open an accessible Cordic web page in desktop Chrome. Start with a simple change to text, spacing or a visible list.

  2. Describe and preview

    Describe the change in your Tweaksy account. Build it with the extension and check the preview in the original tab.

  3. Approve and share

    Approve the exact version to enable it. Your other logged-in computers receive it when they sync, on matching pages.

Questions about Tweaksy and Cordic

Which Cordic screens can I use?

Cordic offers several products and booking channels; a cloud-hosted installation is not proof of a browser interface. These examples are conditional on an actual Cordic web page in desktop Chrome. Installed dispatch clients, remote desktop sessions and mobile apps are outside scope.

Can I modify Cordic without a developer?

For a small change to an accessible browser screen, you can describe what you want in plain English and preview it with Tweaksy. Custom Cordic integrations, new stored fields and background workflows need the product's own configuration or developer tools. Start with the browser requirements above.

Are these ready-made integrations?

These are ideas for changes to request on a browser page, not prebuilt Cordic integrations. The result depends on the page layout, information currently visible and your browser permissions. Preview each change on your own screen.

What information is used to build a change?

Creating a change uses your request and relevant page details, processed by Tweaksy and its AI service. Automatic filtering reduces sensitive information, but visible personal or business details can still be included. The privacy policy explains who handles your data and your choices. Try a demo or a page without confidential information first.

Does this replace Cordic settings or permissions?

No. Tweaksy can adjust a page in your browser; it cannot add server-side fields, retrieve records you cannot access or change account permissions. Review any change affecting page behaviour before approving it.

What happens when Cordic changes its layout?

A saved change may need rebuilding after a software update. Check it on the updated page, switch it off if needed and preview a revised version before approving it again.

Can I use it with colleagues?

Each desktop Chrome using Tweaksy needs the extension and a login to your Tweaksy account, within your plan's computer allowance. Approved changes sync to those computers. Managed browsers may require your administrator to allow the extension.

Start with one screen and one useful change.

Try a clearer label, a larger reference number or a tidier list. Preview it, then decide what to keep.

No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.

Product names belong to their respective owners. Tweaksy is an independent product made by OptiCab Ltd. Listing a product does not imply a partnership, endorsement or verified compatibility with every screen.