In Hyderabad the whole catalogue is a photograph on someone's phone

Selling from images, which no standard system expects

AI automation in Hyderabad is shaped by how the selling actually happens. A customer forwards a photograph and names a quantity, and nothing in that message maps to a product code. The first system worth building turns an image and a line of chat into an order record, with the article identified, the quantity captured and the price confirmed by a person.

Hyderabad's bangle and accessory trade, and a good part of its textile and general wholesale, runs on photographs. A design is shot on a phone, sent to buyers, and ordered against by description. There is often a design number somewhere, but the customer does not use it, because he is looking at a picture.

This is genuinely awkward for anyone selling standard order management software, and it is why so much of it goes unused here. The system expects a code. The conversation contains an image and a sentence. Whoever is answering does the translation manually, from memory, and gets it wrong often enough that returns and disputes are a normal cost of business.

The workable design accepts the way the trade actually behaves. Every design photographed for sale is stored once with its code, its colours and its packing unit attached. When a customer forwards an image, the enquiry is captured with that image attached to it, and where the picture can be matched to a stored design the code is proposed rather than assumed. The person answering confirms with one tap instead of scrolling.

The written confirmation back to the customer is the part that pays. Design code, colour, quantity in the unit you both use, rate and total, sent before anything is packed. Most disputes in this trade are disagreements about what was ordered, and they end when there is a message that says it.

• Every saleable design stored once with code, colours and packing unit
• Enquiries captured with the customer's own image attached to them
• A proposed match rather than an assumed one, confirmed by a person
• Written order confirmation before packing, in the unit the customer uses
• Repeat orders placed against a previous order rather than described again

Fragile goods, cargo and the argument about who broke it

Goods leaving Hyderabad for Karachi, Lahore, Quetta or further go by cargo service, and a proportion of what this city makes is breakable. Bangles arrive short. A carton is crushed. The customer photographs the damage and asks for a credit, and nobody can say whether the breakage happened in packing, in transit, or in the customer's own shop.

That argument is expensive twice over: once in the goods and once in the relationship. It is also almost entirely avoidable with a habit that costs a minute per consignment. Photograph the packed cartons before dispatch, against the consignment number and the cargo receipt. Record the count. Keep both where they can be retrieved in thirty seconds.

Automation's job here is to make the habit stick and the evidence findable. The dispatch record is created when the consignment is booked, the photographs attach themselves to it, the cargo receipt number is read from a photograph of the receipt, and the customer is sent the dispatch details automatically. When a damage claim arrives, it is matched to the same record and both parties are looking at the same evidence.

Where the claim is genuine, this shortens the conversation rather than winning it. That is the correct outcome. A trade that runs on repeat customers is not improved by winning arguments with them, it is improved by settling them quickly.

Supplying retailers across interior Sindh

Hyderabad supplies a long tail of small retailers spread across the districts of interior Sindh. They order by phone, hold running balances, buy in small quantities, and deal with a person rather than with a company. Many of them will never fill in a form, and any plan that assumes otherwise is a plan for a system that gets used by nobody.

The workflows that suit this pattern are conversational and short. An order taken on a call or a voice note is entered once and confirmed in writing. A balance statement goes out on a schedule, in Sindhi or Urdu depending on the customer, with each invoice's age shown, which is a far less awkward way to raise the subject than a phone call. A delivery run is planned by area rather than by whoever asked most recently.

Collection deserves its own record. Cash collected on a route is currently reconciled each evening from a person's memory and a pocket of receipts. Recorded against the customer and the invoice at the moment it is taken, it stops being a monthly source of small discrepancies that nobody can trace.

Two hours from Karachi, and still no office here

Wobble is based in Karachi and works with Hyderabad businesses remotely. There is no office in this city and no local team. The distance is short enough that travel for a scoping session or a handover is straightforward, and it would still be dishonest to describe that as a local presence.

What matters more for a business of this size is scope. Most Hyderabad manufacturers and traders should start with one workflow, not a system: usually order capture and written confirmation, because that is where the disputes and the lost time concentrate. If a supplier proposes a full platform to a business with one counter and a dispatch point, they are selling their own capability rather than solving your problem.

Hold the accounts in your own name, keep administrator access, and judge the first phase by whether your own staff use it without being reminded.

When the account is the relationship, and software gets in the way

If your designs change constantly and are never photographed in an organised way, the image matching described above will be unreliable, and unreliable matching is worse than none because it invites a wrong confirmation. The prerequisite is a shoot and a code for each design, done once and kept up.

If your customer base is small and your orders are large, the manual way is fine and will remain fine. The cost of this trade's informality is proportional to the number of customers, not to the value of the goods.

If your business runs almost entirely on cash and on trust, and there is no appetite to write down balances or terms, then most of the credit and collection workflows here are unavailable. That is a legitimate way to run a business and it should not be talked out of it by a technology supplier.

And if the reason you are considering this is a competitor's website rather than a cost you can name inside your own operation, the honest advice is to wait until you can name it.

How soon it runs, who still confirms, and who keeps the design library

The first week goes on the design library, because nothing on this page works without it: every saleable design stored once with its code, its colours and its packing unit. That is a photography and discipline job rather than a software one, which is why a build here is measured by the state of the catalogue rather than by weeks of engineering. Once it exists, enquiry capture with the customer's own image attached is live inside a fortnight. Image matching follows, once there are enough stored designs for a proposal to be worth making at all.

The match is proposed and never assumed, and that is the design decision the whole thing turns on. A system cannot tell a photograph of your design from a photograph of somebody's copy of it, so it offers candidates and hands it to a person to confirm with one tap. A rate outside the sheet, a credit decision and any damage claim wait for human approval, because those are relationship decisions in a trade that lives on repeat customers rather than on winning arguments.

The design library is the asset, and it belongs to the business rather than to whoever has been carrying the codes in his head. It sits in an account under your own logins alongside the order records and the dispatch photographs, so you own the system and the library survives a supplier, a staff change or a switch of software. Building it is also the piece your own team can do in-house over a few weeks with a phone and a rule about codes, and it is worth doing whether or not anything is automated afterwards. Ibrahim owns build and workflows at Wobble, on the view that a catalogue nobody in the building can update is a catalogue that stops being true by next season.

The nearest published engagement is Emraan Rajput, a Pakistani fashion business grown from performance ads into a full operating system across creative, Shopify operations, callers and copy. That is retail rather than wholesale and the distance is real, because nothing on the work page sells forty dozen against a photograph. Wobble works from Karachi, bills month to month, across 25 engagements in six countries.

Common questions

Our customers order from photographs, not codes. Can that be automated?

Partly, and the design has to accept the trade as it is. Every saleable design is stored once with its code, colours and packing unit. When a customer forwards an image, the enquiry is captured with that image attached, and where it can be matched to a stored design the code is proposed for a person to confirm rather than assumed. The written confirmation back to the customer is what removes most disputes.

How do we deal with damage claims on fragile goods?

With evidence created before dispatch rather than argued afterwards. Photograph the packed cartons and record the count against the consignment number and cargo receipt, and keep both retrievable. A system's contribution is making that habit stick and the evidence findable, and matching an incoming claim to the same record so both parties are looking at the same thing.

Can we send balance statements to small retailers automatically?

Yes, and it is usually the least awkward way to raise the subject. Statements go on a schedule, in the language the customer uses, with each invoice's age shown. It is worth pairing that with recording collections against the customer and invoice at the moment cash is taken on a route, which removes the small monthly discrepancies that currently get reconciled from memory.

Do you have an office in Hyderabad?

No. Wobble is based in Karachi and works with Hyderabad businesses remotely, with no local team. Karachi is close enough that travel for a scoping session or a handover is easy, and that still does not amount to a local presence. Judge the arrangement on scope, on who holds the accounts, and on whether your own staff use the first phase without being reminded.

What should a small trading business here start with?

One workflow, almost always order capture with a written confirmation before packing. It addresses the most common loss in this trade, which is a dispute about what was ordered, and it can be judged within weeks. A full platform sold to a business with one counter and a dispatch point is a supplier showing off their range.

We run mostly on cash and trust. Does any of this apply?

Some of it does and some of it does not, and a supplier should say which. Order capture and dispatch evidence apply regardless. Credit limits, balance statements and structured collections assume you are willing to write balances and terms down. If you are not, those workflows are not available to you, and that is a legitimate way to run a business rather than a problem to be fixed.