Deep parts integrations are valuable
I will say that first because they are. Being connected directly to suppliers can save serious time.
A useful integration can reduce searching and make ordering easier. There is no point pretending otherwise just because Mozomay has taken a different route so far.
The core product still has to stand on its own
Mozomay Workflow does not currently depend on an external parts API to make the parts section useful. That was deliberate.
A third party can change its API, its commercial terms or the way the connection works. Your basic parts process should not become useless because something outside your garage management system moved.
Search without leaving the job
Inside the parts section of a job, you enter the part you are looking for and search for it. Mozomay can use the vehicle details, part name and part number to help find it online.
You can save the relevant part information back against the job. You are still working from the same place, and the context stays attached to the car instead of disappearing into somebody's browser history.
Mozomay Workflow v1.5 goes further
Mozomay Workflow v1.5 is being built to bring much richer parts functionality. But we did not want the thinking to stop at the standard LKQ and GSF connections.
Those integrations are useful, but they are not the only problems a partsman has. We targeted the actual pain points around finding the right part, knowing which job it belongs to, keeping the number and information together, seeing what is outstanding, and letting reception understand the delay without constantly asking.
The integration is not the product
A supplier connection is one part of a much bigger job. The difficult bit is making sure the correct item is found, ordered, recognised when it arrives and visible to everybody whose day changes if it is late or wrong.
The integration is not the product. The workflow around the person ordering the parts is.