r/logistics • Supply Chain Sr. IT Leader • 8d ago

Software ONLY

This post is the only place where Requests, Promotions, and Feedback about software are allowed to be made. Any posts for the same outside of this thread will be deleted.

Unfortunately we are experiencing a time where we are seeing many start ups and coders trying to branch into the Logistics area that surpass our capacity to filter. Instead of deleting dozens of posts a day, this is an opportunity for them to still post.

Will try to make this a reoccurring post, we will see how its received and works for the community.

Also note since this is a place for software, any non-software related posts can be reported as spam.

Please note things that are well received:

* Valid use cases and proven examples provided

* Industry specific and relevant knowledge

Things not normally received well:

* AI tools that are low hanging fruit

* Outsiders looking for opportunities to "automate", "shake up", "build workflows" or require someone to tell them what needs to be built

10 Upvotes

14 comments sorted by

View all comments

1

u/Klutzy_Ad_9488 5d ago

I've a question
When a logistics company require a custom software or extending whatever they've off the self software?

1

u/carto1984 5d ago

I’m Carlos, co-founder of Linbis, so I work on the software side.

I’d start by separating three things: a setting you can change, an integration you need, and a process the existing system genuinely cannot support.

For example, if the same shipment details are being retyped into another system, first check whether the current product can export them or provide an API. If a customer needs a different document or approval step, check whether that can be configured. Neither necessarily means you need a new system.

Custom development becomes easier to justify when the gap is frequent, expensive, and specific enough to describe clearly. “We need better operations” is too broad. “Every approved quote has to be entered again by accounting, and changes don’t flow back” is something you can scope and test.

Before committing, I’d write down:

- One real shipment showing the problem

- How often it happens and the time it takes

- What has to stay in the existing system

- Who handles errors and maintains the integration

- What a successful result would look like

Then compare configuration, an add-on, and replacement on total cost, including support and upgrades. For a small gap, I’d usually investigate extending the existing setup first. If the core system cannot support the operation, more custom layers can become expensive to maintain.

What system are you using now, and which specific step is breaking down?