Production Checklist Before deploying Nord Inventory to production, verify the following. Server oxmysql starts before Nord Inventory. Database connectivity is stable. Resource folder remains named nord_inventory. Framework detection reports the intended bridge. Admin ACE/license fallback is limited to trusted staff. Config.Debug is disabled unless actively diagnosing. Inventory Player inventory persists through disconnect/reconnect. Inventory persists through resource/server restart. Add/remove/move/split operations work correctly. Fast Slots/hotbar and pinned-item rules work. Ground pickup/drop/throw behavior is correct. Container nesting rules match your design. Items Item images exist in the expected location. Internal consumable effects/removal are correct. External exports have the correct resource, export and execution side. External handlers return false only when use should be cancelled. Runtime item names do not conflict with database-authoritative items. Disabled base items remain disabled after restart. Restore returns base items to the original Lua definition. Metadata visibility does not expose internal/sensitive fields. Vehicles Trunks work on common front/rear-storage vehicles. No-trunk vehicles are rejected. Glovebox/trunk capacities match your economy. Addon vehicles have saved placement when required. NPC trunk loot rules are intentional and balanced. Integrations Third-party mutations use Nord server exports. Private stashes validate access server-side. RegisterUsableItem callbacks work after resource restart. External client and server item-use paths are tested separately. Hooks that can block actions are tested for false positives. Nord Staff integration is tested after Nord Inventory starts. Nord CarPlay uses the client carplay export when following the documented install flow. Upgrade-specific Config.Notify, Config.TextUI, Config.Target use the current simple provider format. nord_inventory_disabled_reference_items exists. No stale or mixed files from older installations remain.