# Sepasoft vs. Ignition for MES

**URL:** <https://forum.inductiveautomation.com/t/sepasoft-vs-ignition-for-mes/53675>\
**Category:** Ignition\
**Created:** [December 2, 2021, 3:19pm UTC](https://forum.inductiveautomation.com/t/sepasoft-vs-ignition-for-mes/53675 "2021-12-02T15:19:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gdube](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gdube/32/41701_2.png) [@gdube](https://forum.inductiveautomation.com/u/gdube)\
**Post date:** [July 19, 2023, 12:31pm UTC](https://forum.inductiveautomation.com/t/sepasoft-vs-ignition-for-mes/53675/3 "2023-07-19T12:31:20Z")

</div>

I feel the main advantage of Sepasoft is the database structure, and an object model to perform/save operations and track lots. You'll still do a lot of scripting. And if you're dealing with lots that may go negative (Qty \< 0) because your physical qty/weight tracking isn't perfect, you'll have a few headaches.

You can easily compare the two, just install the Sepasoft modules and spend a few days trying to do basic tasks in it.

Please report back, I'd be glad to see someone reflect on this.

---

_[View the full topic](https://forum.inductiveautomation.com/t/sepasoft-vs-ignition-for-mes/53675)._